From: | Ivan Kartyshov <i(dot)kartyshov(at)postgrespro(dot)ru> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: make async slave to wait for lsn to be replayed |
Date: | 2017-10-23 09:29:03 |
Message-ID: | abcff0b4e3ce1c2a4d14f54e7031dc15@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alexander Korotkov писал 2017-09-26 12:07:
> I propose following syntax options.
>
> WAITLSN lsn;
> WAITLSN lsn TIMEOUT delay;
> WAITLSN lsn INFINITE;
> WAITLSN lsn NOWAIT;
>
> For me that looks rather better. What do you think?
I agree with you, now syntax looks better.
New patch attached to tha mail.
Ants Aasma писал 2017-09-26 13:00:
> Exposing this interface as WAITLSN will encode that visibility order
> matches LSN order. This removes any chance of fixing for example
> visibility order of async/vs/sync transactions. Just renaming it so
> the token is an opaque commit visibility token that just happens to be
> a LSN would still allow for progress in transaction management. For
> example, making PostgreSQL distributed will likely want timestamp
> and/or vector clock based visibility rules.
I'm sorry I did not understand exactly what you meant.
Please explain this in more detail.
--
Ivan Kartyshov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
Attachment | Content-Type | Size |
---|---|---|
waitlsn_11dev_v7.patch | text/x-diff | 23.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Ivan Kartyshov | 2017-10-23 09:42:56 | Re: make async slave to wait for lsn to be replayed |
Previous Message | Amit Langote | 2017-10-23 09:07:20 | Re: [sqlsmith] Failed assertion in adjust_appendrel_attrs_mutator |