| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Sami Imseih <samimseih(dot)pg(at)gmail(dot)com> |
| Cc: | sirisha chamarthi <sirichamarthi22(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Alexander Korotkov <akorotkov(at)postgresql(dot)org> |
| Subject: | Re: WAIT FOR command should do some query jumbling |
| Date: | 2026-08-31 02:43:52 |
| Message-ID: | apTqaBVPqLfhg5lS@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Aug 30, 2026 at 05:27:59PM -0500, Sami Imseih wrote:
> 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?
I can see the lack of normalization for the LSN as a bug, but the
option patterns in a WITH clause is IMO more debatable. I think that
we should collect more data from the field before setting down on a
behavior we may regret. I can partially get behind a normalization of
the timeout, but I am less clear about the MODE and NO_THROW, as it
could be useful to split them.
In terms of v19, it seems to me that just ignoring the LSN part is
enough as a LSN is a moving target, so I would agree about using v1
for now, backpatch it down to v19. We should consider some of the
patterns covered by v2 once we know more about how users use this
feature.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2026-08-31 02:48:38 | Re: pgstat: Flush some statistics within running transactions, take 2 |
| Previous Message | Bertrand Drouvot | 2026-08-31 02:39:19 | Report relation extension blockers within parallel lock groups |