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

From Dmitry Dolgov
Subject Re: Fwd: Re: proposal: schema variables
Date
Msg-id l254xqf2rvnpa7znemlajchutp7zc56czus34onsmutblylaum@7u652q7bxjye
Whole thread Raw
In response to Re: Fwd: Re: proposal: schema variables  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
> On Fri, Jan 17, 2025 at 11:01:41AM GMT, Bruce Momjian wrote:
> 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?

+1 into the bucket "want committed" from me as well. Throughout the
review process I've stumbled upon a few cases in my own projects, where
it would be useful.



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: [PATCH] Hex-coding optimizations using SVE on ARM.
Next
From: Masahiko Sawada
Date:
Subject: Re: Skip collecting decoded changes of already-aborted transactions