Re: Intermittent buildfarm failures on wrasse
От | Peter Geoghegan |
---|---|
Тема | Re: Intermittent buildfarm failures on wrasse |
Дата | |
Msg-id | CAH2-WzmO_vNK-hsjWVGXWBsON2Rya3fZ7qKxaMxhJzAE=wdCvA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Intermittent buildfarm failures on wrasse (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: Intermittent buildfarm failures on wrasse
|
Список | pgsql-hackers |
On Thu, Apr 14, 2022 at 9:48 AM Andres Freund <andres@anarazel.de> wrote: > I think it might be worth leaving in, but let's debate that separately? > I'm thinking of something like the attached. The current convention for the "extra" ereport()s that VACUUM VERBOSE outputs at INFO elevel is to use DEBUG2 elevel in all other cases (these extra messages are considered part of VACUUM VERBOSE output, but are *not* considered part of the autovacuum log output). It looks like you're changing the elevel convention for these "extra" messages with this patch. That might be fine, but don't forget about similar ereports() in vacuumparallel.c. I think that the elevel should probably remain uniform across all of these messages. Though I don't particular care if it's DEBUG2 or DEBUG5. -- Peter Geoghegan
В списке pgsql-hackers по дате отправления: