From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: System views for versions reporting |
Date: | 2024-10-16 13:31:58 |
Message-ID: | adb7b7e8-7ffb-4afd-bb38-a0c0c2351485@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/16/24 08:47, Peter Eisentraut wrote:
> On 06.10.24 17:36, Dmitry Dolgov wrote:
>> Based on the feedback in [1], here is my attempt at implementing system
>> views for versions reporting. It adds pg_system_versions for showing
>> things like core version, compiler, LLVM, etc, and pg_system_libraries
>> for showing linked shared objects.
>
> Is a system view the right interface? For example, in pgbouncer we just
> added it to the version output:
>
> $ pgbouncer --version
> PgBouncer 1.18.0
> libevent 2.1.12-stable
> adns: c-ares 1.19.0
> tls: OpenSSL 3.3.2 3 Sep 2024
>
> That way, you can get this information without having to start a server
> instance. (Maybe you can't start a server instance because it just
> crashed because of some library version issue ...)
While it is also useful to be able to get the info without being able to
start the server, I think that would be an addition not a replacement.
When you have a fleet with no direct access to run shell commands, being
able to get this info via SQL is valuable.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2024-10-16 13:54:57 | Re: Doc: typo in config.sgml |
Previous Message | Robert Haas | 2024-10-16 12:54:02 | Re: Proposal to Enable/Disable Index using ALTER INDEX |