Hi,
On 2019-09-22 11:45:05 -0400, Jeff Janes wrote:
> On Fri, Sep 20, 2019 at 6:25 PM Andres Freund wrote:
> > Hi,
> > >Is there an innocent explanation for this? I thought logical
> > >replication
> > >slots provided an iron-clad guarantee that WAL would be retained until
> > >it
> > >was no
On Fri, Sep 20, 2019 at 6:25 PM Andres Freund wrote:
> Hi,
>
> On September 20, 2019 5:45:34 AM PDT, Jeff Janes
> wrote:
> >While testing something else (whether "terminating walsender process
> >due to
> >replication timeout" was happening spuriously), I had logical
> >replication
> >set up
On Fri, Sep 20, 2019 at 11:27 AM Tomas Vondra
wrote:
> >
> >Is there an innocent explanation for this? I thought logical replication
> >slots provided an iron-clad guarantee that WAL would be retained until it
> >was no longer needed. I am just using pub/sub, none of the lower level
> >stuff.
Hi,
On September 20, 2019 5:45:34 AM PDT, Jeff Janes wrote:
>While testing something else (whether "terminating walsender process
>due to
>replication timeout" was happening spuriously), I had logical
>replication
>set up streaming a default pgbench transaction load, with the publisher
>being
While testing something else (whether "terminating walsender process due to
replication timeout" was happening spuriously), I had logical replication
set up streaming a default pgbench transaction load, with the publisher
being 13devel-e1c8743 and subscriber being 12BETA4. Eventually I started
