Re: [HACKERS] make async slave to wait for lsn to be replayed
От
Andres Freund
Тема
Re: [HACKERS] make async slave to wait for lsn to be replayed
Дата
Msg-id
20180302004714.nf6mntdwdjsbexmk@alap3.anarazel.de
Ответ на
Список
Дерево обсуждения
make async slave to wait for lsn to be replayed Ivan Kartyshov <i.kartyshov@postgrespro.ru>
Re: make async slave to wait for lsn to be replayed Thomas Munro <thomas.munro@enterprisedb.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed Ivan Kartyshov <i.kartyshov@postgrespro.ru>
Re: [HACKERS] make async slave to wait for lsn to be replayed Thom Brown <thom@linux.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed Thomas Munro <thomas.munro@enterprisedb.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed David Steele <david@pgmasters.net>
Re: [HACKERS] make async slave to wait for lsn to be replayed Ivan Kartyshov <i.kartyshov@postgrespro.ru>
Re: [HACKERS] make async slave to wait for lsn to be replayed Masahiko Sawada <sawada.mshk@gmail.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed Ivan Kartyshov <i.kartyshov@postgrespro.ru>
Re: [HACKERS] make async slave to wait for lsn to be replayed Thomas Munro <thomas.munro@enterprisedb.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed i.kartyshov@postgrespro.ru
Re: [HACKERS] make async slave to wait for lsn to be replayed David Steele <david@pgmasters.net>
Re: make async slave to wait for lsn to be replayed David Steele <david@pgmasters.net>
Re: [HACKERS] make async slave to wait for lsn to be replayed Robert Haas <robertmhaas@gmail.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed Craig Ringer <craig@2ndquadrant.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed i.kartyshov@postgrespro.ru
Re: [HACKERS] make async slave to wait for lsn to be replayed Ants Aasma <ants.aasma@eesti.ee>
Re: [HACKERS] make async slave to wait for lsn to be replayed Robert Haas <robertmhaas@gmail.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed Thomas Munro <thomas.munro@enterprisedb.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed Alexander Korotkov <a.korotkov@postgrespro.ru>
Re: [HACKERS] make async slave to wait for lsn to be replayed Ivan Kartyshov <i.kartyshov@postgrespro.ru>
Re: [HACKERS] make async slave to wait for lsn to be replayed Ivan Kartyshov <i.kartyshov@postgrespro.ru>
Re: [HACKERS] make async slave to wait for lsn to be replayed Alexander Korotkov <a.korotkov@postgrespro.ru>
Re: [HACKERS] make async slave to wait for lsn to be replayed Ivan Kartyshov <i.kartyshov@postgrespro.ru>
Re: [HACKERS] make async slave to wait for lsn to be replayed Ants Aasma <ants.aasma@eesti.ee>
Re: [HACKERS] make async slave to wait for lsn to be replayed Robert Haas <robertmhaas@gmail.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed Ivan Kartyshov <i.kartyshov@postgrespro.ru>
Re: [HACKERS] make async slave to wait for lsn to be replayed Stephen Frost <sfrost@snowman.net>
Re: [HACKERS] make async slave to wait for lsn to be replayed Simon Riggs <simon@2ndquadrant.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed Stephen Frost <sfrost@snowman.net>
Re: [HACKERS] make async slave to wait for lsn to be replayed Ants Aasma <ants.aasma@eesti.ee>
Re: [HACKERS] make async slave to wait for lsn to be replayed Michael Paquier <michael.paquier@gmail.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed Simon Riggs <simon@2ndquadrant.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed Robert Haas <robertmhaas@gmail.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed Simon Riggs <simon@2ndquadrant.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed Andres Freund <andres@anarazel.de>
Re: [HACKERS] make async slave to wait for lsn to be replayed Ivan Kartyshov <i.kartyshov@postgrespro.ru>
Re: [HACKERS] make async slave to wait for lsn to be replayed Michael Paquier <michael@paquier.xyz>
Re: Re: [HACKERS] make async slave to wait for lsn to be replayed David Steele <david@pgmasters.net>
Re: Re: [HACKERS] make async slave to wait for lsn to be replayed Fujii Masao <masao.fujii@gmail.com>
Re: [HACKERS] make async slave to wait for lsn to be replayed David Steele <david@pgmasters.net>
Re: [HACKERS] make async slave to wait for lsn to be replayed Michael Paquier <michael@paquier.xyz>
Re: [HACKERS] make async slave to wait for lsn to be replayed Dmitry Ivanov <d.ivanov@postgrespro.ru>
Re: [HACKERS] make async slave to wait for lsn to be replayed Simon Riggs <simon@2ndquadrant.com>
Re: make async slave to wait for lsn to be replayed Thomas Munro <thomas.munro@enterprisedb.com>
Re: make async slave to wait for lsn to be replayed Craig Ringer <craig@2ndquadrant.com>
Re: make async slave to wait for lsn to be replayed Ivan Kartyshov <i.kartyshov@postgrespro.ru>
On 2018-02-02 19:41:37 +0000, Simon Riggs wrote: > On 2 February 2018 at 18:46, Robert Haas wrote: > > On Fri, Feb 2, 2018 at 3:46 AM, Simon Riggs wrote: > >> In PG11, I propose the following command, sticking mostly to Ants' > >> syntax, and allowing to wait for multiple events before it returns. It > >> doesn't hold snapshot and will not get cancelled by Hot Standby. > >> > >> WAIT FOR event [, event ...] options > >> > >> event is > >> LSN value > >> TIMESTAMP value > >> > >> options > >> TIMEOUT delay > >> UNTIL TIMESTAMP timestamp > >> (we have both, so people don't need to do math, they can use whichever > >> they have) > > > > WAIT FOR TIMEOUT sounds a lot like SELECT pg_sleep_for(), and WAIT > > UNTIL TIMESTAMP sounds a lot like SELECT pg_sleep_until(). > > Yes, it sounds very similar. It's the behavior that differs; I read > and agreed with yours and Thomas' earlier comments on that point. > > As pointed out upthread, the key difference is whether it gets > cancelled on Hot Standby and whether you can call it in a non-READ > COMMITTED transaction. Given that nobody has updated the patch or even discussed doing so, I assume this would CF issue should now appropriately be classified as returned with feedback? Greetings, Andres Freund
В списке pgsql-hackers по дате отправления