Re: Fwd: Re: proposal: schema variables - Mailing list pgsql-hackers

From Gilles Darold
Subject Re: Fwd: Re: proposal: schema variables
Date
Msg-id 82636335-245d-4de0-9c21-a94dbf9ff5d0@darold.net
Whole thread Raw
In response to Re: Fwd: Re: proposal: schema variables  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Le 17/01/2025 à 19:01, Bruce Momjian a écrit :
> On Fri, Jan 17, 2025 at 04:55:07PM +0100, Pavel Stehule wrote:
>> pá 17. 1. 2025 v 16:35 odesílatel Bruce Momjian <bruce@momjian.us> napsal:
>>
>>      So this feature would be like global GUC variables, with permission
>>      control?
>>
>> + types and domain type check - holds data in binary form - there are not
>> conversions binary, text
>> + it is declared - so less space for misuse is there. Custom GUC are absolutely
>> tolerant
>> + it is a fully database object, only owner can alter it,  and event triggers
>> are supported, sinval
>> + possibility to set mutability, default value
> Okay, good summary.  Now, can people give feedback that they would want
> this committed to PostgreSQL?
>

For me, this is a must have. Not only because of the huge amount of time 
that we will save in migration to PostgreSQL (i know that this is not an 
argument) but because the only way we have to emulate such feature is to 
use custom configuration directives or a PL language that allows global 
variable. I have question almost every week on how to do that and the 
only answer I have is do this ugly pl/pgsql coding. It will be nice to 
have a feature to do that. Thanks Pavel and all involved in this 
implementation.

-- 
Gilles Darold
http://www.darold.net/




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Old BufferDesc refcount in PrintBufferDescs and PrintPinnedBufs
Next
From: Sergey Tatarintsev
Date:
Subject: Re: create subscription with (origin = none, copy_data = on)