On Wed, Sep 9, 2026 at 9:57 PM Sami Imseih <[email protected]> wrote: > > Thanks for the feedback. > > > Thanks for raising this! I agree this may need to be harnessed. If we > > change this line, we might also want to modify the > > read-your-writes-consistency chapter. > > <sect2 id="read-your-writes-consistency"> > > <title>Read-Your-Writes Consistency</title> > > Yes, that needs to mention the COMMIT LSN explicitly. > > > I am also wondering whether a example like this is helpful, though it is > > somehow duplicated with the existing one: > > postgres=# BEGIN; > > BEGIN > > postgres=*# UPDATE movie SET genre = 'Dramatic' WHERE genre = 'Drama'; > > UPDATE 100 > > postgres=*# COMMIT; > > COMMIT > > postgres=# SELECT pg_current_wal_insert_lsn(); > > Rather than change the example, just updated the explanation of the > example with the proper commit wording. > > 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. -- Regards, Xuneng Zhou HighGo Software Co., Ltd.
