Re: [HACKERS] make async slave to wait for lsn to be replayed
От | Kartyshov Ivan |
---|---|
Тема | Re: [HACKERS] make async slave to wait for lsn to be replayed |
Дата | |
Msg-id | 2c7ed9b13cf776c918234153d95a1b3c@postgrespro.ru обсуждение исходный текст |
Ответ на | Re: [HACKERS] make async slave to wait for lsn to be replayed (Alexander Korotkov <aekorotkov@gmail.com>) |
Ответы |
Re: [HACKERS] make async slave to wait for lsn to be replayed
|
Список | pgsql-hackers |
On 2023-11-27 03:08, Alexander Korotkov wrote: > I've retried my case with v6 and it doesn't fail anymore. But I > wonder how safe it is to reset xmin within the user-visible function? > We have no guarantee that the function is not called inside the > complex query. Then how will the rest of the query work with xmin > reset? Separate utility statement still looks like more safe option > for me. As you mentioned, we can`t guarantee that the function is not called inside the complex query, but we can return the xmin after waiting. But you are right and separate utility statement still looks more safe. So I want to bring up the discussion on separate utility statement again. -- Ivan Kartyshov Postgres Professional: www.postgrespro.com
В списке pgsql-hackers по дате отправления: