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

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Oleg Serov <oleg(at)slapdash(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:13:25
Message-ID: 209CB91E-B785-4BEB-8CAC-4A2FEF700D1B@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stefen Hillman 2021-11-08 19:16:57 Logical Replication - Type messages?
Previous Message Tom Lane 2021-11-08 19:05:41 Re: libpq: How to cancel a COPY ... TO statement?