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 16:01:41 |
Message-ID: | Z4p-5R34LHYGO90V@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
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?
--
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Anthonin Bonnefoy | 2025-01-17 16:01:53 | Re: Accept recovery conflict interrupt on blocked writing |
Previous Message | vignesh C | 2025-01-17 16:00:42 | Re: create subscription with (origin = none, copy_data = on) |
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2025-01-17 16:10:47 | Re: Fwd: Re: proposal: schema variables |
Previous Message | Pavel Stehule | 2025-01-17 15:55:07 | Re: Fwd: Re: proposal: schema variables |