Re: Forbid to DROP temp tables of other sessions

From: "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Daniil Davydov <3danissimo(at)gmail(dot)com>, Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Forbid to DROP temp tables of other sessions
Date: 2024-11-23 18:13:02
Message-ID: 44B342BD-156C-4131-B2C0-845BF41B6B74@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 22 Nov 2024, at 03:02, Andres Freund <andres(at)anarazel(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Abhishek Kumar 2024-11-24 00:31:09 Integrating HLL cardinality estimates with join operator estimation
Previous Message Michail Nikolaev 2024-11-23 16:20:41 Re: [BUG?] check_exclusion_or_unique_constraint false negative