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

From: Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>
To: Xuneng Zhou <xunengzhou(at)gmail(dot)com>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Improve WAIT FOR read-your-writes consistency doc
Date: 2026-09-10 18:19:59
Message-ID: CAN12+Y+Pod3fcibF1s7ezxAaj+3wu3XxykVBMaUghZGvt0gxHA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks!

> > WDYT of the attached?
>
> Just a trivial comment:
>
> + This is achieved by the following steps. After committing the write
> + operations on the primary, the application retrieves a WAL location
> + that is at or after the transaction's <literal>COMMIT</literal> record,
> + using a function call like this.
>
> We might need to specify the word 'end' clearly to avoid
> misunderstanding the LSN position as the beginning of the commit
> record.
>
> at or after the *end* of the write transaction’s COMMIT record.

I rather the comment be more high-level, and we just need to convey
that the function should be called after the commit.

See the attached.

--
Sami Imseih
Amazon Web Services (AWS)

Attachment Content-Type Size
v2-0001-Clarify-WAIT-FOR-read-your-writes-documentation.patch application/octet-stream 4.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2026-09-10 18:21:53 Re: Rename PqMsg_Progress to PqMsg_ParallelWorkerProgress
Previous Message Robert Haas 2026-09-10 18:13:15 Re: pg_*_advice: tsv load failure, etc.