Re: Why does [auto-]vacuum delay not report a wait event?

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why does [auto-]vacuum delay not report a wait event?
Date: 2020-03-22 00:59:25
Message-ID: CAH2-Wzm7Zx3hkNOPNsspErNObHAr-1As-s_S2ZeEnto7=Y=NTQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Mar 21, 2020 at 5:53 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> My comment is entirely unrelated to GIN, but about the way the delay infrastructure manages state (in global vars).

The fact that ginInsertCleanup() uses "stats != NULL" to indicate
whether it is being called from within VACUUM or not is surely
relevant, or at least relevant to the issue that Mahendra just
reported. shiftList() relies on this directly already.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2020-03-22 01:26:59 Re: Additional size of hash table is alway zero for hash aggregates
Previous Message Andres Freund 2020-03-22 00:53:45 Re: Why does [auto-]vacuum delay not report a wait event?