Re: [HACKERS] make async slave to wait for lsn to be replayed - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [HACKERS] make async slave to wait for lsn to be replayed
Date
Msg-id CANP8+j+ELxyoVECyYagioUUkYTkJCiZwzPHc4S9V0LJS9r5GNw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] make async slave to wait for lsn to be replayed  (Stephen Frost <sfrost@snowman.net>)
Responses Re: [HACKERS] make async slave to wait for lsn to be replayed  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On 22 January 2018 at 23:21, Stephen Frost <sfrost@snowman.net> wrote:

>> It sounds reasonable. I can offer the following version.
>>
>> WAIT  LSN  lsn_number;
>> WAIT  LSN  lsn_number  TIMEOUT delay;
>> WAIT  LSN  lsn_number  INFINITE;
>> WAIT  LSN  lsn_number  NOWAIT;
>>
>>
>> WAIT  [token]  wait_value [option];
>>
>> token - [LSN, TIME | TIMESTAMP | CSN | XID]
>> option - [TIMEOUT | INFINITE | NOWAIT]
>>
>> Ready to listen to your suggestions.
>
> There were a few different suggestions made, but somehow this thread
> ended up in Needs Review again while still having LSNs.  I've changed it
> back to Waiting for Author since it seems pretty unlikely that using LSN
> is going to be acceptable based on the feedback.

I agree with the need for a separate command rather than a function.

I agree that WAIT LSN is good syntax because this allows us to wait
for something else in future.

Without having reviewed the patch, I think we want this feature in PG11.

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] generated columns
Next
From: Merlin Moncure
Date:
Subject: Re: JIT compiling with LLVM v9.0