Re: Improve WAIT FOR read-your-writes consistency doc

From: Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: Xuneng Zhou <xunengzhou(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Improve WAIT FOR read-your-writes consistency doc
Date: 2026-09-16 22:41:59
Message-ID: CAN12+YLcpE98fFuBiL3es=vLvckDVM9474Nhz7r=T3Z-xCjB-w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 16, 2026 at 5:30 PM Alexander Korotkov <aekorotkov(at)gmail(dot)com>
wrote:

> On Tue, Sep 15, 2026 at 4:27 PM Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>
> wrote:
> > Attached is a rebase.
>
> I've made this following changes to the patch.
> 1) Change <command>WAIT FOR</command> back to <command>WAIT</command>
> (see a23ab4862cfe).
> 2) In the example, app gets lsn at or after *the end* of the relevant
> write transaction's COMMIT record. If we say lsn at the COMMIT record
> then it might be interpreted as at he beginning of that record (and
> that is wrong).
>
> I'm going to push this if no objections.

LGTM

Sami

>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2026-09-16 23:00:05 Re: PG19: two RI fast-path issues found while testing the batching revert
Previous Message Jacob Champion 2026-09-16 22:41:32 Re: [PATCH] Explain what the default output_plugin_libraries do