Re: Question: Is it possible to get the new xlog position after query execution?

From: Oleg Serov <oleg(at)slapdash(dot)com>
To: Christophe Pettus <xof(at)thebuild(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Question: Is it possible to get the new xlog position after query execution?
Date: 2021-11-08 19:47:23
Message-ID: CAH2JyMQczhDZiePH=nPcakS9UWi-KRsuNs3BWaPHpv0dxGtWYw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Nov 8, 2021 at 2:14 PM Christophe Pettus <xof(at)thebuild(dot)com> wrote:

>
>
> > On Nov 8, 2021, at 10:03, Oleg Serov <oleg(at)slapdash(dot)com> 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 <role> SET synchronous_commit = 'on';
>
> That way, the users that require it have it, but other users do not.

I'm sorry, when I mean users, I mean application end-user (e.g. john(at)doe(dot)com),
not the postgres role.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Christophe Pettus 2021-11-08 20:03:32 Re: Question: Is it possible to get the new xlog position after query execution?
Previous Message Stefen Hillman 2021-11-08 19:16:57 Logical Replication - Type messages?