| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Online PostgreSQL version() updates |
| Date: | 2026-04-01 14:38:22 |
| Message-ID: | 408d8baf-b87a-4248-8e47-864d2b8f3511@proxel.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/1/26 1:35 PM, Andreas Karlsson wrote:
> On 4/1/26 12:48 PM, Matthias van de Meent wrote:
>> Attached is a patch that allows superusers to update the version() of
>> their running system with a simple SQL call: SELECT
>> pg_update_version(version_num, 'version_short', 'the full version()
>> outout'). Running backends will automatically get updated without
>> impacting their active workloads, and new backends will immediately
>> notice the new version().
>
> Thanks for the patch!
>
> Some small quibbles:
Another thing: What should the return value be? Right now
pgsql_update_version() returns the new value for version_short, but that
feels not that useful and pretty arbitrary. Maybe we should simply have
it return void?
--
Andreas Karlsson
Percona
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Jones | 2026-04-01 14:39:56 | Re: WIP - xmlvalidate implementation from TODO list |
| Previous Message | Álvaro Herrera | 2026-04-01 14:27:18 | Re: table AM option passing |