From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | 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 14:35:40 |
Message-ID: | 72830.1729089340@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Joe Conway <mail(at)joeconway(dot)com> writes:
> On 10/16/24 08:47, Peter Eisentraut wrote:
>> 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.
Yeah. In addition, I envisioned that this might include information
that's only readily available at runtime. Don't have a concrete
example at hand (-ENOCAFFEINE) but I think that --version is
necessarily going to be exceedingly constrained in what it can do.
Another problem is that, just like with version(), there is already
code making assumptions about what --version will output. Most of
that is under our control, but perhaps not all. The main value
of a new system view, IMV, is that it's a completely green field
for us to define the contents of.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2024-10-16 14:44:27 | Re: Doc: shared_memory_size_in_huge_pages with the "SHOW" command. |
Previous Message | Ashutosh Bapat | 2024-10-16 14:06:29 | Misleading error "permission denied for table" |