From: | Julien Rouhaud <rjuju123(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 16:10:47 |
Message-ID: | Z4qBB2alzlV8CZFF@jrouhaud |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
On Fri, Jan 17, 2025 at 11:01:41AM -0500, 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?
I unsurprisingly would really like to see it committed, for all the reasons
Pavel mentioned. It would have helped me on various projects many times.
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Rasheed | 2025-01-17 16:29:07 | Re: [PATCH] Add get_bytes() and set_bytes() functions |
Previous Message | Anthonin Bonnefoy | 2025-01-17 16:01:53 | Re: Accept recovery conflict interrupt on blocked writing |
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2025-01-17 16:43:13 | Re: Fwd: Re: proposal: schema variables |
Previous Message | Bruce Momjian | 2025-01-17 16:01:41 | Re: Fwd: Re: proposal: schema variables |