Alvaro Herrera <[EMAIL PROTECTED]> writes:
> It seems like I'll have to decouple autovacuum PGPROC's from
> autovacuum's own shared memory. The most sensible way to do this seems
> to be to store them in ProcGlobal, along with the regular backend's
> PGPROCs. Is everyone OK with this plan?
> Note that this will mean that those PGPROCs will be protected by the
> same spinlock that protects the other PGPROCs. I can't think of any
> reason why this would be a problem, but if you think otherwise please
> speak up.
I thought the separate pool of PGPROCs was a bit weird. If you're going
back to a common pool, I'm all for it.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
