| From: | Sami Imseih <samimseih(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | sirisha chamarthi <sirichamarthi22(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Alexander Korotkov <akorotkov(at)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: WAIT FOR command should do some query jumbling |
| Date: | 2026-08-30 22:27:59 |
| Message-ID: | CAN12+YJc7znA+VJRw_CyuQ1xri__uzsj1+x_LDjno2Z_vK0Njg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
One observation with this approach is at times option can have different
> meanings
> and that may be lost during jumbling. For example, in the WAL FOR LSN case,
> 4 different MODEs are defined with different semantics and this patch does
> not differentiate.
>
> WAIT FOR LSN $1 WITH (MODE $2, TIMEOUT $3, NO_THROW)
>
I thought about this, but did not think it will be useful to keep MODE
without normalization, since we are normalizing the LSN. But, perhaps
others have a different opinion?
--
Sami Imseih
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2026-08-31 00:21:07 | Re: Add starelid, attnum to pg_stats and leverage this in pg_dump |
| Previous Message | sirisha chamarthi | 2026-08-30 21:34:14 | Re: WAIT FOR command should do some query jumbling |