| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: shared-memory based stats collector - v70 |
| Date: | 2022-04-13 23:34:32 |
| Message-ID: | CAKFQuwZn3CU6ptdt-u02RPbL0dNV20gLoW2wN2Ch6AuFHL_AHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 5, 2022 at 8:00 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> Here comes v70:
>
>
One thing I just noticed while peeking at pg_stat_slru:
The stats_reset column for my newly initdb'd cluster is showing me
"2000-01-01 00:00:00" (v15). I was expecting null, though a non-null value
restriction does make sense. Neither choice is documented though.
Based upon my expectation I checked to see if v14 reported null, and thus
this was a behavior change. v14 reports the initdb timestamp (e.g.,
2022-04-13 23:26:48.349115+00)
Can we document the non-null aspect of this value (pg_stat_database is
happy being null, this seems to be a "fixed" type behavior) but have it
continue to report initdb as its initial value?
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-04-13 23:38:06 | Re: Intermittent buildfarm failures on wrasse |
| Previous Message | Bruce Momjian | 2022-04-13 23:18:37 | Re: Temporary file access API |