Re: Skip vacuum log report code in lazy_scan_heap() if possible

From: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>, Andres Freund <andres(at)anarazel(dot)de>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, 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-12-03 17:46:51
Message-ID: 7A37FF82-DA2C-4625-BE57-B4FBF7EFDD00@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/3/21, 7:40 AM, "Peter Geoghegan" <pg(at)bowt(dot)ie> wrote:
> If my patch to unite vacuum verbose and the autovacuum logging gets
> in, then this issue also goes away.

Perhaps this patch should be marked Rejected in favor of that one,
then.

Nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bossart, Nathan 2021-12-03 17:55:04 Re: should we document an example to set multiple libraries in shared_preload_libraries?
Previous Message Tom Lane 2021-12-03 17:45:34 Re: Remove extra Logging_collector check before calling SysLogger_Start()