From: Tom Lane <tgl@sss.pgh.pa.us>
To: Teja Jakkidi <teja.jakkidi05@gmail.com>
Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Vacuum and analyze for objects on physical stand by dbs
Date: Fri, 17 Feb 2023 21:27:53 -0500
Message-ID: <2914859.1676687273@sss.pgh.pa.us> (raw)
In-Reply-To: <FEFF9714-8435-4FE4-9F7D-034F687BEF06@gmail.com>
References: <FEFF9714-8435-4FE4-9F7D-034F687BEF06@gmail.com>
Teja Jakkidi <teja.jakkidi05@gmail.com> writes:
> I have an environment with 1 primary and 2 physical stand by instances. We have manually analyzed/ vacuumed tables on primary db recently. Later when we checked analyze, vacuum on stand by dbs in pg_stat_user_tables it returns null. Will vacuum/ analyze do not replicate to stand by instances?? Do we have to run separately on all the Stand by instances??
The data changes will propagate, but those action counters are just
maintained locally to the primary server. Their values on a hot
standby are meaningless, probably always zero, because a standby
*can't* change the data on its own.
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, teja.jakkidi05@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Vacuum and analyze for objects on physical stand by dbs
In-Reply-To: <2914859.1676687273@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