Re: [HACKERS] make async slave to wait for lsn to be replayed

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Ivan Kartyshov <i(dot)kartyshov(at)postgrespro(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] make async slave to wait for lsn to be replayed
Date: 2018-02-01 14:47:35
Message-ID: CANP8+j+ELxyoVECyYagioUUkYTkJCiZwzPHc4S9V0LJS9r5GNw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 22 January 2018 at 23:21, Stephen Frost <sfrost(at)snowman(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2018-02-01 14:51:17 Re: JIT compiling with LLVM v9.0
Previous Message Peter Eisentraut 2018-02-01 14:29:09 Re: [HACKERS] generated columns