Re: Forbid to DROP temp tables of other sessions

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Daniil Davydov <3danissimo(at)gmail(dot)com>
Cc: Steven Niu <niushiji(at)gmail(dot)com>, "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(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" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Forbid to DROP temp tables of other sessions
Date: 2025-03-17 15:09:12
Message-ID: CAKFQuwYTVwe_WGq22+O7CoztffbrhNh4bQfuSU2Kr6RQLQE5DA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Monday, March 17, 2025, Daniil Davydov <3danissimo(at)gmail(dot)com> wrote:

>
> >
> > 2."you have not any temporary relations" --> "you have no any temporary
> > relations"
> I am not an English speaker, but it seems that "have not" would be
> more correct. Someone has to judge us :)
>
>
Both are not good.

โ€œpg_temp was specified but it contains no relationsโ€ [1]

But why are we promoting this situation to an error? It should be a
relation not found error just like any other and not its own special case.
The fact we create pg_temp only as it is needed is an implementation detail
that should not be visible to the user. Either by saying pg_temp not found
(possibly at this point) or pretending it does and letting the relation
name lookup produce the error.

David J.

[1] It isnโ€™t part of the style guide but I donโ€™t think we use โ€œyouโ€ to
directly refer to the query author in error messages.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-03-17 15:14:51 Re: Disabling vacuum truncate for autovacuum
Previous Message Jacob Champion 2025-03-17 15:08:30 Re: [PoC] Federated Authn/z with OAUTHBEARER