Re: [HACKERS] make async slave to wait for lsn to be replayed - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] make async slave to wait for lsn to be replayed
Date
Msg-id 27171.1586439221@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] make async slave to wait for lsn to be replayed  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: [HACKERS] make async slave to wait for lsn to be replayed  (Alexey Kondratov <a.kondratov@postgrespro.ru>)
List pgsql-hackers
Fujii Masao <masao.fujii@oss.nttdata.com> writes:
> On 2020/04/09 16:11, Kyotaro Horiguchi wrote:
>> At Wed, 08 Apr 2020 16:35:46 -0400, Tom Lane <tgl@sss.pgh.pa.us> wrote in
>>> Why is this getting grafted onto BEGIN/START TRANSACTION in the
>>> first place?

>> The rationale for not being a fmgr function is stated in the following
>> comments. [...]

> This issue happens because the function is executed after BEGIN? If yes,
> what about executing the function (i.e., as separate transaction) before BEGIN?
> If so, the snapshot taken in the function doesn't affect the subsequent
> transaction whatever its isolation level is.

I wonder whether making it a procedure, rather than a plain function,
would help any.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: Planning counters in pg_stat_statements (using pgss_store)
Next
From: Erik Rijkers
Date:
Subject: Re: [Proposal] Global temporary tables