From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
---|---|
To: | Greg Nancarrow <gregn4422(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Skip vacuum log report code in lazy_scan_heap() if possible |
Date: | 2021-10-29 17:47:19 |
Message-ID: | 13CA6501-D0E1-40CD-A540-59CBC38D163E@amazon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/29/21, 3:54 AM, "Greg Nancarrow" <gregn4422(at)gmail(dot)com> wrote:
> When recently debugging a vacuum-related issue, I noticed that there
> is some log-report processing/formatting code at the end of
> lazy_scan_heap() that, unless the vacuum VERBOSE option is specified,
> typically results in no log output (as the log-level is then DEBUG2).
> I think it is worth skipping this code if ultimately nothing is going
> to be logged (and I found that even for a tiny database, a VACUUM may
> execute this code hundreds of times).
> I have attached a simple patch for this.
I think this logging only happens once per table, so I'm not sure it's
really worth it to short-circuit here. If it was per-page, IMO there
would be a much stronger case for it. That being said, I don't think
the proposed patch would hurt anything.
Nathan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-10-29 18:00:14 | Better localization of errors in plpgsql variable initialization |
Previous Message | Jacob Champion | 2021-10-29 17:38:20 | Re: [PATCH] Support pg_ident mapping for LDAP |