Horton
Menu

Re: RFC: Logging plan of the running query

Atsushi Torikoshi <torikoshia.tech@gmail.com>

View thread
From: Atsushi Torikoshi <torikoshia.tech@gmail.com>
To: Lukas Fittl <lukas@fittl.com>
Cc: torikoshia <torikoshia@oss.nttdata.com>, pgsql-hackers@lists.postgresql.org, samimseih@gmail.com, destrex271@gmail.com, robertmhaas@gmail.com
Date: 2026-06-08T11:48:55Z
Lists: pgsql-hackers 
On Mon, Jun 8, 2026 at 3:08 PM Lukas Fittl <lukas@fittl.com> wrote:
> I was reminded about this patch at PG DATA in Chicago last week, and
> figured I'd see if I can contribute a review / help move this forward
> in PG20.
Thanks for your help! I really appreciate it.

> First of all, find attached a v54 that is rebased over changes late in
> the PG19 cycle, with other minimal fixes:

It may take me a few days, but I'll take a look at the updated patch.

--
Atsushi Torikoshi

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. ecpg: Catch zero-length Unicode identifiers correctly

  2. Improve warning message in pg_signal_backend()

  3. Add assert to ensure that page locks don't participate in deadlock cycle.