Re: New IndexAM API controlling index vacuum strategies - Mailing list pgsql-hackers

From Tom Lane
Subject Re: New IndexAM API controlling index vacuum strategies
Date
Msg-id 933377.1617665367@sss.pgh.pa.us
Whole thread Raw
In response to Re: New IndexAM API controlling index vacuum strategies  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: New IndexAM API controlling index vacuum strategies
Re: New IndexAM API controlling index vacuum strategies
List pgsql-hackers
Peter Geoghegan <pg@bowt.ie> writes:
> Do you think that it's okay that we rely on the propagation of global
> state to parallel workers on Postgres 13? Don't we need something like
> my fixup commit 49f49def on Postgres 13 as well? At least for the
> EXEC_BACKEND case, I think.

Uh ... *what* propagation of global state to parallel workers?  Workers
fork off from the postmaster, not from their leader process.

(I note that morepork is still failing.  The other ones didn't report
in yet.)

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Covering SPGiST index
Next
From: "osumi.takamichi@fujitsu.com"
Date:
Subject: RE: Stronger safeguard for archive recovery not to miss data