From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jerry Sievers <gsievers19@comcast.net>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Does raising maintenance_work_mem get seen by an already running aucovac?
Date: Wed, 25 Jan 2023 16:36:03 -0500
Message-ID: <2845694.1674682563@sss.pgh.pa.us> (raw)
In-Reply-To: <m0y1pqcxl9.fsf@comcast.net>
References: <m0y1pqcxl9.fsf@comcast.net>
Jerry Sievers <gsievers19@comcast.net> writes:
> There's a long running anti-wrap autovac that we'd rather let finish but
> on the server instance, I found maintenance_work_mem rather low and thus
> raised it in postgresql.comf, reloaded and confirmed that my interactive
> session saw the change.
> Can a running autovac make use of this or should I either wait it out or
> cancel and let it restart when ready?
Looks like an autovac worker will notice postgresql.conf changes once
per table:
/*
* Perform operations on collected tables.
*/
foreach(cell, table_oids)
{
...
/*
* Check for config changes before processing each collected table.
*/
if (ConfigReloadPending)
ProcessConfigFile(PGC_SIGHUP);
If it is stuck on a particularly enormous table, you might be best off
to kill it, but otherwise I'd let it go.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, gsievers19@comcast.net, pgsql-admin@lists.postgresql.org
Subject: Re: Does raising maintenance_work_mem get seen by an already running aucovac?
In-Reply-To: <2845694.1674682563@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox