From: | obi reddy <obireddy(dot)g1997(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Teja Jakkidi <teja(dot)jakkidi05(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Vacuum and analyze for objects on physical stand by dbs |
Date: | 2023-02-18 15:09:28 |
Message-ID: | CAO7L2Zw=nXLdBQKKxNpPdiiMT4JDBhjxfTSQRP0ibizTrpe0ig@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2023-02-20 13:52:03 | Re: Is it possible to log long running recursive/internal postgresql queries? |
Previous Message | Tom Lane | 2023-02-18 02:27:53 | Re: Vacuum and analyze for objects on physical stand by dbs |