| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Intermittent buildfarm failures on wrasse |
| Date: | 2022-04-14 16:21:54 |
| Message-ID: | CAH2-Wz=apXJfVcydkN_4rhnvdkOqWjMLq4nmehso4Zzh-eXMvg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 14, 2022 at 9:18 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> I wonder if we should make VACUUM log the VERBOSE output at DEBUG1
> unconditionally. This is like the third bug where we needed that
> information, and it's practically impossible to include in regression
> output. Then we'd know what the xid horizon is, whether pages were
> skipped, etc.
I like the idea of making VACUUM log the VERBOSE output as a
configurable user-visible feature. We'll then be able to log all
VACUUM statements (not just autovacuum worker VACUUMs).
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2022-04-14 16:22:15 | Re: make MaxBackends available in _PG_init |
| Previous Message | Andres Freund | 2022-04-14 16:18:50 | Re: Intermittent buildfarm failures on wrasse |