From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Fwd: Re: proposal: schema variables |
Date: | 2025-01-17 17:47:52 |
Message-ID: | l254xqf2rvnpa7znemlajchutp7zc56czus34onsmutblylaum@7u652q7bxjye |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
> 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(at)momjian(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2025-01-17 17:48:44 | Re: Skip collecting decoded changes of already-aborted transactions |
Previous Message | Nathan Bossart | 2025-01-17 17:15:29 | Re: [PATCH] Hex-coding optimizations using SVE on ARM. |
From | Date | Subject | |
---|---|---|---|
Next Message | Wolfgang Walther | 2025-01-17 20:20:03 | Re: Fwd: Re: proposal: schema variables |
Previous Message | Laurenz Albe | 2025-01-17 16:43:13 | Re: Fwd: Re: proposal: schema variables |