Re: Intermittent buildfarm failures on wrasse
От | Peter Geoghegan |
---|---|
Тема | Re: Intermittent buildfarm failures on wrasse |
Дата | |
Msg-id | CAH2-WzkqC-7ooG99Ai0vPyV1Vj4zx4nqn1i-9ijXiNcrBSrMvQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Intermittent buildfarm failures on wrasse (Peter Geoghegan <pg@bowt.ie>) |
Список | pgsql-hackers |
On Thu, Apr 14, 2022 at 10:07 AM Peter Geoghegan <pg@bowt.ie> wrote: > 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. Also, don't forget to do something here, with the assertion and with the message: if (verbose) { /* * Aggressiveness already reported earlier, in dedicated * VACUUM VERBOSE ereport */ Assert(!params->is_wraparound); msgfmt = _("finished vacuuming \"%s.%s.%s\": index scans: %d\n"); } else if (params->is_wraparound) { Presumably we will need to report on antiwraparound-ness in the verbose-debug-elevel-for-autovacuum case (and not allow this assertion to fail). -- Peter Geoghegan
В списке pgsql-hackers по дате отправления: