Re: pgsql: Add support for temporary replication slots

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Add support for temporary replication slots
Date: 2016-12-12 23:39:13
Message-ID: 15713.1481585953@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

I wrote:
> Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> writes:
>> Attached is the fixed test using the loop from test_extensions (and yes
>> I would have missed the pg_stat_clear_snapshot() call without the hint,
>> thanks :) ).

> Pushed, thanks.

Hm, buildfarm says this didn't fix it. Where exactly does the dropping
of the slot happen ... is it not complete by the time the backend exits?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Petr Jelinek 2016-12-13 00:05:08 Re: pgsql: Add support for temporary replication slots
Previous Message Robert Haas 2016-12-12 20:59:15 pgsql: Remove should_free arguments to tuplesort routines.

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2016-12-12 23:44:46 Re: exposing wait events for non-backends (was: Tracking wait event for latches)
Previous Message Petr Jelinek 2016-12-12 23:38:26 Re: snapbuild woes