| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Online PostgreSQL version() updates |
| Date: | 2026-04-01 12:01:51 |
| Message-ID: | 9A9D654D-A666-4943-B1FC-1E086AAC68C0@yandex-team.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 1 Apr 2026, at 15:48, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> 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')
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2026-04-01 12:10:39 | Re: POC: Parallel processing of indexes in autovacuum |
| Previous Message | Ashutosh Bapat | 2026-04-01 11:59:13 | Re: Better shared data structure management and resizable shared data structures |