Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.21\))
Subject: Re: Online PostgreSQL version() updates
From: Andrey Borodin <x4mmm@yandex-team.ru>
In-Reply-To: 
 <CAEze2WjgxD-uZrjiD7Gtp2gy=ztAOTU+xyLNJg6saYG4erP_=w@mail.gmail.com>
Date: Wed, 1 Apr 2026 17:01:51 +0500
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A9D654D-A666-4943-B1FC-1E086AAC68C0@yandex-team.ru>
References: 
 <CAEze2WjgxD-uZrjiD7Gtp2gy=ztAOTU+xyLNJg6saYG4erP_=w@mail.gmail.com>
To: Matthias van de Meent <boekewurm+postgres@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/9A9D654D-A666-4943-B1FC-1E086AAC68C0%40yandex-team.ru>
Precedence: bulk


> On 1 Apr 2026, at 15:48, Matthias van de Meent =
<boekewurm+postgres@gmail.com> wrote:
>=20
> 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')

While I find this proposal very useful, I think the interface can be =
improved.

Consider SELECT pg_update_version(commit_hash) so we can do stuff like
SELECT pg_update_version('REL_18_2') or SELECT =
pg_update_version('HEAD~10000').
In future we can even create a bisect facility, so when user encounters =
a bug in their production they can iterate over several commits to trace =
root cause.


Best regards, Andrey Borodin.=