Re: Call lazy_check_wraparound_failsafe earlier for parallel vacuum

From: "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Call lazy_check_wraparound_failsafe earlier for parallel vacuum
Date: 2022-11-11 15:28:11
Message-ID: 2D785AF5-677B-4194-B5D1-6316EC72DB72@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Yeah, it's a little inconsistent.

Yes, this should be corrected by calling the failsafe
inside the parallel vacuum loops and handling the case by exiting
the loop and parallel vacuum if failsafe kicks in.

> I meant that there should definitely be a check between each round of
> index scans (one index scan here affects each and every index). Doing
> more than a single index scan is presumably rare, but are likely
> common among VACUUM operations that take an unusually long time --
> which is where the failsafe is relevant.

Ah, OK. I was confused by the terminology. I read "index scans" as a single
Index scan rather than a index scan cycle.

FWIW, even in the parallel case, the failsafe is checked after every index
scan cycle.

> Want to have a go at writing a patch for that?

Yes, I can.

Regards,

Sami Imseih
Amazon Web Services (AWS)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Berg 2022-11-11 15:59:06 Re: [PATCH] Support % wildcard in extension upgrade filenames
Previous Message Tom Lane 2022-11-11 15:24:34 Re: A problem about join ordering