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

From Anna Akenteva
Subject Re: [HACKERS] make async slave to wait for lsn to be replayed
Date
Msg-id d3ff2e363af60b345f82396992595a03@postgrespro.ru
Whole thread Raw
In response to Re: [HACKERS] make async slave to wait for lsn to be replayed  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: [HACKERS] make async slave to wait for lsn to be replayed  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [HACKERS] make async slave to wait for lsn to be replayed  (a.pervushina@postgrespro.ru)
List pgsql-hackers
On 2020-04-08 04:09, Kyotaro Horiguchi wrote:
> How about something like the follows.
> 
> BEGIN AFTER ColId Sconst
> BEGIN FOLOWING ColId Sconst
> 
> UNTIL <absolute time>;
> LIMIT BY <interval>;
> WITHIN Iconst;
> 
> regards.

I like your suggested keywords! I think that "AFTER" + "WITHIN" sound 
the most natural. We could completely give up the LSN keyword for now. 
The final command could look something like:

BEGIN AFTER ‘0/303EC60’ WITHIN '5 seconds';
or
BEGIN AFTER ‘0/303EC60’ WITHIN 5000;

I'd like to hear others' opinions on the syntax as well.

-- 
Anna Akenteva
Postgres Professional:
The Russian Postgres Company
http://www.postgrespro.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Parallel copy
Next
From: Robert Haas
Date:
Subject: Re: where should I stick that backup?