| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | a(dot)pervushina(at)postgrespro(dot)ru |
| Cc: | Anna Akenteva <a(dot)akenteva(at)postgrespro(dot)ru>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Alexey Kondratov <a(dot)kondratov(at)postgrespro(dot)ru>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Ivan Kartyshov <i(dot)kartyshov(at)postgrespro(dot)ru>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [HACKERS] make async slave to wait for lsn to be replayed |
| Date: | 2020-11-16 11:31:29 |
| Message-ID: | CAPpHfdvSwC0ZRsKybAn=OKfHjPXmQOUV_jf+cLkZ+dOde30=rw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi!
On Mon, Nov 16, 2020 at 1:09 PM <a(dot)pervushina(at)postgrespro(dot)ru> wrote:
> I've changed the BEGIN WAIT FOR LSN statement to core functions
> pg_waitlsn, pg_waitlsn_infinite and pg_waitlsn_no_wait.
> Currently the functions work inside repeatable read transactions, but
> waitlsn creates a snapshot if called first in a transaction block, which
> can possibly lead the transaction to working incorrectly, so the
> function gives a warning.
>
> Usage examples
> ==========
> select pg_waitlsn(‘LSN’, timeout);
> select pg_waitlsn_infinite(‘LSN’);
> select pg_waitlsn_no_wait(‘LSN’);
The name pg_waitlsn_no_wait() looks confusing. I've tried to see how
it's documented, but the patch doesn't contain documentation...
------
Regards,
Alexander Korotkov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Rijkers | 2020-11-16 12:26:36 | doc CREATE INDEX |
| Previous Message | Pavel Borisov | 2020-11-16 11:05:03 | Re: Evaluate expression at planning time for two more cases |