| 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-09 13:57:05 |
| Message-ID: | CAN12+Y+RaD-Q1BugF9vboPrCQjLLBRp-FAy=CBK0v5dpQ3ux1Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Sami
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Clarify-WAIT-FOR-read-your-writes-documentation.patch | application/octet-stream | 4.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Xuneng Zhou | 2026-09-09 14:00:55 | Re: Reject WAIT FOR earlier in transaction-snapshot mode |
| Previous Message | Nikolay Samokhvalov | 2026-09-09 13:31:01 | Re: Add contrib module pg_stat_log: cumulative statistics about server log messages |