| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, pgsql-hackers(at)postgresql(dot)org, mmelihmutlu(at)gmail(dot)com |
| Subject: | Re: pg_stat_io for the startup process |
| Date: | 2023-04-25 22:45:55 |
| Message-ID: | ZEhYI8HfPT6Pm3F3@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 25, 2023 at 04:00:24PM -0400, Robert Haas wrote:
> ISTM that it's pretty desirable to do something about this. If the
> process isn't going to report statistics properly, at least remove it
> from the view. If it can be made to report properly, that would be
> even better. But shipping a new view with information that will nearly
> always be zeroes instead of real data seems like a bad call, even if
> there are existing cases that have the same problem.
Agreed that reporting no information may be better than reporting
incorrect information, even if it means an extra qual. As mentioned
upthread, if this requires an extra design piece, adding the correct
information had better be pushed to v17~.
Perhaps an open item should be added?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-04-25 23:04:23 | Re: pg_stat_io for the startup process |
| Previous Message | Michael Paquier | 2023-04-25 21:39:21 | Re: Allow pg_archivecleanup to remove backup history files |