| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Sami Imseih <samimseih(dot)pg(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-17 06:38:06 |
| Message-ID: | CAPpHfdsG5cxqpjk4wa+WbZd29zcJSa9050H1OovcMsXg7Ce+fA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 17, 2026 at 1:42 AM Sami Imseih <samimseih(dot)pg(at)gmail(dot)com> wrote:
> 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
Thank you, pushed.
------
Regards,
Alexander Korotkov
Supabase
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2026-09-17 06:38:34 | Re: WAIT FOR NO_THROW option could use some documentation |
| Previous Message | Alexandre Felipe | 2026-09-17 06:27:47 | Re: SLOPE - Planner optimizations on monotonic expressions. |