> On Jan 5, 2023, at 19:38, Bhautik Chudasama
> wrote:
>
> Does it mean when we commit transaction, client will wait until all replicas
> successfully committed the transaction.
It depends. If all the settings are the defaults, no, the client won't wait
for the replicas to acknowledge the
> On Jan 5, 2023, at 16:03, Ron wrote:
>
> Even in asynchronous replication?
Yes. Asynchronous replication controls when the client doing the transaction
is told that the transaction is complete; it doesn't allow for dirty reads on
either the primary or secondary.
On 1/5/23 14:09, Christophe Pettus wrote:
On Jan 5, 2023, at 12:07, Louis Laborde wrote:
Are PG replicas updated atomically following the same transactions boundaries
as the source DB ?
Yes. The same transactional guarantees apply to the replica as do to the
original transactions on the pri
> On Jan 5, 2023, at 12:07, Louis Laborde wrote:
>
> Are PG replicas updated atomically following the same transactions boundaries
> as the source DB ?
Yes. The same transactional guarantees apply to the replica as do to the
original transactions on the primary.
Are PG replicas updated atomically following the same transactions
boundaries as the source DB ?
For example, if 2 rows from a named table are updated atomically (with a
transaction) in the source DB, is there a guarantee that both
changes will be done atomically in a replica, or is there a time wi
