Message-ID: <408d8baf-b87a-4248-8e47-864d2b8f3511@proxel.se>
Date: Wed, 1 Apr 2026 16:38:22 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Online PostgreSQL version() updates
From: Andreas Karlsson <andreas@proxel.se>
To: Matthias van de Meent <boekewurm+postgres@gmail.com>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
References: 
 <CAEze2WjgxD-uZrjiD7Gtp2gy=ztAOTU+xyLNJg6saYG4erP_=w@mail.gmail.com>
 <3922da25-1dbc-4780-92c3-c2460aecbed5@proxel.se>
Content-Language: en-US
In-Reply-To: <3922da25-1dbc-4780-92c3-c2460aecbed5@proxel.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/408d8baf-b87a-4248-8e47-864d2b8f3511%40proxel.se>
Precedence: bulk

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