Re: Forbid to DROP temp tables of other sessions
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Daniil Davydov <3danissimo@gmail.com>
Cc: Steven Niu <niushiji@gmail.com>,
"Andrey M. Borodin" <x4mmm@yandex-team.ru>, Andres Freund <andres@anarazel.de>, Thomas Munro <thomas.munro@gmail.com>, Rafia Sabih <rafia.pghackers@gmail.com>,
Michael Paquier <michael@paquier.xyz>, Tom Lane <tgl@sss.pgh.pa.us>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2025-03-18T23:32:19Z
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 →
-
pg_basebackup: Add missing PQclear in error path
- a19db0827496 18.0 landed
On Mon, Mar 17, 2025 at 9:27 PM Daniil Davydov <3danissimo@gmail.com> wrote: > Hi, > > On Tue, Mar 18, 2025 at 2:36 AM David G. Johnston > <david.g.johnston@gmail.com> wrote: > > > > "I want to give a better error message" is not a good enough reason to > change this long-standing behavior in a back-patchable bug fix. > >.... and I do not agree that it is an improvement worth making in HEAD. > > OK, In this case I'd rather agree. > I'm probably done trying to help with this one - it's beyond my ability and desire to contribute to meaningfully. It seems to need to be escalated if the regression has a chance of being understood and fixed. Some good candidates for helping out are copied already so I'm just hoping one or more of them chimes in. I'll repeat my suggestion to start a new thread and let this one die. The answer to $subject is no. David J.