| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Robins Tharakan <tharakan(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add pg_accept_connections_start_time() for better uptime calculation |
| Date: | 2025-02-17 00:53:06 |
| Message-ID: | 695475.1739753586@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> On Sun, Feb 16, 2025 at 11:47:46AM +0100, Laurenz Albe wrote:
>> Would it make sense to add that information to the output of
>> "pg_ctl status" as well? Perhaps as a new option, so that default output
>> format doesn't change.
> A separate function that only returns the open-for-connection time has
> benefits on its own because its execution can be granted to separate
> users, without knowing about the full contents of postmaster.pid.
> That last part should matter for cloud vendors. And this file only
> knows about MyStartTime.
Yeah. Making that happen would require extending the contents of
postmaster.pid, which is likely to break assorted peoples' tooling.
I doubt that this feature clears the bar for justifying that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2025-02-17 01:06:15 | Re: Improve statistics estimation considering GROUP-BY as a 'uniqueiser' |
| Previous Message | Tom Lane | 2025-02-17 00:50:18 | Re: BackgroundPsql swallowing errors on windows |