Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1pKjvC-0006zu-8S
	for pgsql-admin@arkaria.postgresql.org; Wed, 25 Jan 2023 17:50:54 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1pKjvB-00023j-5D
	for pgsql-admin@arkaria.postgresql.org; Wed, 25 Jan 2023 17:50:53 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <cyber.hunko@comcast.net>)
	id 1pKjvA-00021l-6C
	for pgsql-admin@lists.postgresql.org; Wed, 25 Jan 2023 17:50:52 +0000
Received: from resqmta-c1p-024060.sys.comcast.net ([2001:558:fd00:56::3])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <cyber.hunko@comcast.net>)
	id 1pKjv7-0004R0-3L
	for pgsql-admin@lists.postgresql.org; Wed, 25 Jan 2023 17:50:50 +0000
Received: from resomta-c1p-023409.sys.comcast.net ([96.102.18.228])
	by resqmta-c1p-024060.sys.comcast.net with ESMTP
	id KiAipHCL8eG0qKjv3pCDyi; Wed, 25 Jan 2023 17:50:45 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;
	s=20190202a; t=1674669045;
	bh=B+NeVsUPpL7vmiufHWQ4bn+pbQd8iiawLxynxb88OjQ=;
	h=Received:Received:Received:From:To:Subject:Date:Message-ID:
	 MIME-Version:Content-Type:Xfinity-Spam-Result;
	b=RraHpj9wjPGeAglPzLF9KXlNJAq8mRASF1xCSN0AGjYZWg7ToKORHjE4YR8j+FRCJ
	 /z03/h0Q+TgoYro/9uBb8NeFS91qx9/PgkftP9LId1mYcIGyF5gbVjWQCD/pw93jRL
	 8VwoYkHcVe+gBtg+yfU4mC0U2MlYoxUAUHADPV9L7CkAuyXqwu5+lsbShJHZnvlzyA
	 MjKcBQ6js2how0xCNtj/pEkWXFQW89enf6BxjbEprXENKlmPFop4oTHGuwR34B5rCA
	 +YLyDgZgR6T+Q5992wY3KU/zKuf+ZvnrW6hvb+aolSEyiE1fn1pSU2FlcaStk9/iQm
	 r4j/reJ8BAa6g==
Received: from R9N0YC2TC3.localdomain
 ([IPv6:2601:249:8780:7950:fd85:63d2:464f:61ea])
	by resomta-c1p-023409.sys.comcast.net with ESMTPA
	id Kjv1pXSfLJHanKjv2pfhei; Wed, 25 Jan 2023 17:50:45 +0000
X-Xfinity-VMeta: sc=0.00;st=legit
Received: by R9N0YC2TC3.localdomain (Postfix, from userid 503)
	id 42F071195E2A; Wed, 25 Jan 2023 11:50:42 -0600 (CST)
From: Jerry Sievers <gsievers19@comcast.net>
To: pgsql-admin@lists.postgresql.org
Subject: Does raising maintenance_work_mem get seen by an already running
 aucovac?
Date: Wed, 25 Jan 2023 11:50:42 -0600
Message-ID: <m0y1pqcxl9.fsf@comcast.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (darwin)
MIME-Version: 1.0
Content-Type: text/plain
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Archived-At: 
 <https://www.postgresql.org/message-id/m0y1pqcxl9.fsf%40comcast.net>
Precedence: bulk

Groovy admins,

This is on Pg11 (shameful, I know !).

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?

The vacuum progress view shows that it's finished the heap and I guess
toast, but is now working through the indexes.

Thx