Re: Forbid to DROP temp tables of other sessions

Andrey Borodin <x4mmm@yandex-team.ru>

From: "Andrey M. Borodin" <x4mmm@yandex-team.ru>

To: Andres Freund <andres@anarazel.de>

Cc: Thomas Munro <thomas.munro@gmail.com>, Daniil Davydov <3danissimo@gmail.com>, Rafia Sabih <rafia.pghackers@gmail.com>, Michael Paquier <michael@paquier.xyz>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org

Date: 2024-11-23T18:13:02Z

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 22 Nov 2024, at 03:02, Andres Freund <andres@anarazel.de> wrote:
> 
> I don't
> love having to put RELATION_IS_OTHER_TEMP() checks everywhere either.

+1. I do not understand why this restriction (protecting temp tables from access) is a responsibility of the buffer manager.

Actually, I like the idea that superuser knows better what to do.
What if we say it's not a bug, but a feature. Will it break some contracts with user or some functionality?

It seems that protection of temp tables should belong to ACL stuff. And in a logic of this subsystem would be natural to just allow superuser do whatever they want with.

Is it some lunatic idea? Or does it make some sense?

Best regards, Andrey Borodin.