Re: Question: Is it possible to get the new xlog position after query execution?
От
Christophe Pettus
Тема
Re: Question: Is it possible to get the new xlog position after query execution?
Дата
Msg-id
209CB91E-B785-4BEB-8CAC-4A2FEF700D1B@thebuild.com
Ответ на
Список
Дерево обсуждения
Question: Is it possible to get the new xlog position after query execution? Oleg Serov <oleg@slapdash.com>
Re: Question: Is it possible to get the new xlog position after query execution? "Peter J. Holzer" <hjp-pgsql@hjp.at>
Re: Question: Is it possible to get the new xlog position after query execution? Oleg Serov <oleg@slapdash.com>
Re: Question: Is it possible to get the new xlog position after query execution? "Peter J. Holzer" <hjp-pgsql@hjp.at>
Re: Question: Is it possible to get the new xlog position after query execution? Oleg Serov <oleg@slapdash.com>
Re: Question: Is it possible to get the new xlog position after query execution? Christophe Pettus <xof@thebuild.com>
Re: Question: Is it possible to get the new xlog position after query execution? Oleg Serov <oleg@slapdash.com>
Re: Question: Is it possible to get the new xlog position after query execution? Christophe Pettus <xof@thebuild.com>
Re: Question: Is it possible to get the new xlog position after query execution? Oleg Serov <oleg@slapdash.com>
Re: Question: Is it possible to get the new xlog position after query execution? Christophe Pettus <xof@thebuild.com>
> On Nov 8, 2021, at 10:03, Oleg Serov wrote: > That does not seem to be feasible for our application. Using synchronous commit affects performance and really makes replication not really useful... What we want to achieve is to have a consistent DB state across all connections for master and replica per user. If other users see something outdated, is OK. Synchronous commit can be turned on and off per-user: ALTER ROLE SET synchronous_commit = 'on'; That way, the users that require it have it, but other users do not.
В списке pgsql-general по дате отправления