public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Pavel Stehule <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Fwd: Re: proposal: schema variables
Date: Fri, 17 Jan 2025 10:35:48 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAFj8pRAki6SGw2Dw-73ubQoDY9yPvfUQBjqr_LN35T7YBcsxmQ@mail.gmail.com>
References: <CAFj8pRChgOLa2i0PVu-Zoss4q8k1ojPu_Ax-CksTkOWDTye9pQ@mail.gmail.com>
<CAFj8pRCpAV5N9q5q+JenC=MWup2gVCWi7ZkOM4F2mbUT=Bp4UQ@mail.gmail.com>
<CAFj8pRCwddC_o1FMyp_mMCyzzuvU7a0f+1X3tHRKmaFhK2K7jw@mail.gmail.com>
<[email protected]>
<CAFj8pRDncxFC+CPy5xoun00uzAOaiyKAkvfby94LfqQuVa4EFA@mail.gmail.com>
<[email protected]>
<CAFj8pRA8U8ARQ+2Y3kc7BUB-J3LzraQ4kn__Y5LK3mevY_xijQ@mail.gmail.com>
<[email protected]>
<CAFj8pRDTGh2DzTkYaAg2EdTsezU-CRSCM-CsfvHvx6JAD1=xdQ@mail.gmail.com>
<CAFj8pRAki6SGw2Dw-73ubQoDY9yPvfUQBjqr_LN35T7YBcsxmQ@mail.gmail.com>
On Fri, Jan 17, 2025 at 04:32:07PM +0100, Pavel Stehule wrote:
> This discussion was around 2017 when I wrote a proposal and I hadn't a feeling
2017 is seven years ago so it would be good to get current feedback on
the desirability of this feature.
> There is one stronger argument for session variables - we are missing global
> temporary tables. It is a real
> limit and more times I found users with bloated pg_class, pg_attributes due
> using temp tables. I don't believe
> so we can have a global temp table - it is a significantly more difficult task
> than session variables. At the end
> session variables are trivial against global temp tables, and can replace
> global temp tables in some use cases.
> And the solution can be nicer, cleaner, safer than with a workaround based on
> GUC.
So this feature would be like global GUC variables, with permission
control?
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
view thread (439+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Fwd: Re: proposal: schema variables
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox