From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Improve handling of parameter differences in physical replication
Date: Thu, 27 Feb 2020 14:37:24 +0100
Message-ID: <c46df4ab-ac96-0c3e-fb48-1670d44d1a97@2ndquadrant.com> (raw)
In-Reply-To: <27894a76-d498-f3fd-d77f-7c03140fbfe9@oss.nttdata.com>
References: <4ad69a4c-cc9b-0dfe-0352-8b1b0cd36c7b@2ndquadrant.com>
<27894a76-d498-f3fd-d77f-7c03140fbfe9@oss.nttdata.com>
On 2020-02-27 11:13, Fujii Masao wrote:
>> Btw., I think the current setup is slightly buggy. The MaxBackends value that is used to size shared memory is computed as MaxConnections + autovacuum_max_workers + 1 + max_worker_processes + max_wal_senders, but we don't track autovacuum_max_workers in WAL.
> Maybe this is because autovacuum doesn't work during recovery?
Autovacuum on the primary can use locks or xids, and so it's possible
that the standby when processing WAL encounters more of those than it
has locally allocated shared memory to handle.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, masao.fujii@oss.nttdata.com
Subject: Re: Improve handling of parameter differences in physical replication
In-Reply-To: <c46df4ab-ac96-0c3e-fb48-1670d44d1a97@2ndquadrant.com>
* 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