Re: WAIT FOR command should do some query jumbling

From: Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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>, Nathan Bossart <nathandbossart(at)gmail(dot)com>
Subject: Re: WAIT FOR command should do some query jumbling
Date: 2026-08-31 12:20:21
Message-ID: CAN12+YJk+ZDdiZn7na-X94pspTVPi=r_9YGXpdOuiFkdNn0BsA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> I see the traction here, but I cannot really get fully convinced by a
> grouping of the timeouts without more input. As a whole, I think that
> Sirisha's patch is fine enough on its own.
>

Perhaps LSN is enough for now as it will be the value that will vary the
most with heavy usage. I don't know how often TIMEOUT values will
vary however, so I'll drop the options normalization idea for now.

--
Sami

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2026-08-31 12:26:38 Protocol compression: a fourth design
Previous Message Akshay Joshi 2026-08-31 11:49:33 Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements