Re: Vacuum and analyze for objects on physical stand by dbs

Thanks Tom and Obi.

Hi Obi,

Autovacuum runs as per the parameters that were set. However we were requested to just run vacuum (not full) and analyze on Postgres instances which has stand by instances.

We had run vacuum and analyze on primary and just wondering if we need to run it on stand by too. But looks like Stand bys automatically gets that from primary.

Regards,

J. Teja.

On Feb 18, 2023, at 7:09 AM, obi reddy <obireddy(dot)g1997(at)gmail(dot)com> wrote:



Hi Teja,

Not required to run separately in standby node,


If we run in master node , automatically it will effect in the slave also.are you using vacuum or vacuum full?

Thanks & Regards 


Obireddy.G

On Sat, 18 Feb 2023, 07:58 Tom Lane, <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

Teja Jakkidi <teja(dot)jakkidi05(at)gmail(dot)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