Re: Fwd: Re: proposal: schema variables

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fwd: Re: proposal: schema variables
Date: 2025-01-17 15:35:48
Message-ID: Z4p41KpSENxS0ASL@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

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 <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Do not let urgent matters crowd out time for investment in the future.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2025-01-17 15:35:55 Re: pure parsers and reentrant scanners
Previous Message Pavel Stehule 2025-01-17 15:32:07 Fwd: Re: proposal: schema variables

Browse pgsql-performance by date

  From Date Subject
Next Message Pavel Stehule 2025-01-17 15:55:07 Re: Fwd: Re: proposal: schema variables
Previous Message Pavel Stehule 2025-01-17 15:32:07 Fwd: Re: proposal: schema variables