| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Ivan Kartyshov <i(dot)kartyshov(at)postgrespro(dot)ru>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] make async slave to wait for lsn to be replayed |
| Date: | 2018-02-02 18:46:45 |
| Message-ID: | CA+Tgmoa_gosB4o3jPjs0AjQWuQ2747+3_Zk+Kzbar30+62FCzA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 2, 2018 at 3:46 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> 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().
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2018-02-02 19:41:37 | Re: [HACKERS] make async slave to wait for lsn to be replayed |
| Previous Message | Peter Geoghegan | 2018-02-02 18:38:27 | Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation) |