Re: RFC: Logging plan of the running query
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: torikoshia <torikoshia@oss.nttdata.com>
Cc: pgsql-hackers@lists.postgresql.org, destrex271@gmail.com, Rafael Thofehrn Castro <rafaelthca@gmail.com>
Date: 2025-03-31T19:24:51Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
ecpg: Catch zero-length Unicode identifiers correctly
- a18b6d2dc288 15.0 cited
-
Improve warning message in pg_signal_backend()
- 7fa945b857cc 15.0 cited
-
Add assert to ensure that page locks don't participate in deadlock cycle.
- 72e78d831ab5 13.0 cited
On Fri, Mar 21, 2025 at 8:40 AM torikoshia <torikoshia@oss.nttdata.com> wrote: > Rebased it again. Hi, I apologize for not having noticed this thread sooner. I just became aware of it as a result of a discussion in the hacking Discord server. I think this has got a lot over overlap with the progressive EXPLAIN patch from Rafael Castro, which I have been reviewing, but I am not sure why we have two different patch sets here. Why is that? Thanks, -- Robert Haas EDB: http://www.enterprisedb.com