Re: [HACKERS] make async slave to wait for lsn to be replayed
От | Anna Akenteva |
---|---|
Тема | Re: [HACKERS] make async slave to wait for lsn to be replayed |
Дата | |
Msg-id | d3ff2e363af60b345f82396992595a03@postgrespro.ru обсуждение исходный текст |
Ответ на | Re: [HACKERS] make async slave to wait for lsn to be replayed (Kyotaro Horiguchi <horikyota.ntt@gmail.com>) |
Ответы |
Re: [HACKERS] make async slave to wait for lsn to be replayed
Re: [HACKERS] make async slave to wait for lsn to be replayed |
Список | 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 по дате отправления: