pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Teja Jakkidi <teja.jakkidi05@gmail.com>
To: obi reddy <obireddy.g1997@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Vacuum and analyze for objects on physical stand by dbs
Date: Mon, 20 Feb 2023 13:22:32 -0800
Message-ID: <22FA6562-087D-45F1-8813-9ACF4353417E@gmail.com> (raw)
In-Reply-To: <CAO7L2Zw=nXLdBQKKxNpPdiiMT4JDBhjxfTSQRP0ibizTrpe0ig@mail.gmail.com>
References: <CAO7L2Zw=nXLdBQKKxNpPdiiMT4JDBhjxfTSQRP0ibizTrpe0ig@mail.gmail.com>


--Apple-Mail-9E8FF95A-790D-41DB-9083-A0345E9CBE0A
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">Thanks Tom and Obi.<div><br></div><div>Hi O=
bi,</div><div>Autovacuum runs as per the parameters that were set. However w=
e were requested to just run vacuum (not full) and analyze on Postgres insta=
nces which has stand by instances.</div><div>We had run vacuum and analyze o=
n primary and just wondering if we need to run it on stand by too. But looks=
 like Stand bys automatically gets that from primary.</div><div><br><div dir=
=3D"ltr">Regards,<div>J. Teja.</div></div><div dir=3D"ltr"><br><blockquote t=
ype=3D"cite">On Feb 18, 2023, at 7:09 AM, obi reddy &lt;obireddy.g1997@gmail=
.com&gt; wrote:<br><br></blockquote></div><blockquote type=3D"cite"><div dir=
=3D"ltr">=EF=BB=BF<div dir=3D"auto">Hi Teja,<div dir=3D"auto"><br></div><div=
 dir=3D"auto">Not required to run separately in standby node,</div><div dir=3D=
"auto">If we run in master node , automatically it will effect in the slave a=
lso.are you using vacuum or vacuum full?</div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">Thanks &amp; Regards&nbsp;</div><div dir=3D"auto">Obireddy.G=
</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_a=
ttr">On Sat, 18 Feb 2023, 07:58 Tom Lane, &lt;<a href=3D"mailto:tgl@sss.pgh.=
pa.us">tgl@sss.pgh.pa.us</a>&gt; wrote:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">Teja Jakkidi &lt;<a href=3D"mailto:teja.jakkidi05@gmail.com" target=3D"_b=
lank" rel=3D"noreferrer">teja.jakkidi05@gmail.com</a>&gt; writes:<br>
&gt; I have an environment with 1 primary and 2 physical stand by instances.=
 We have manually analyzed/ vacuumed tables on primary db recently. Later wh=
en we checked analyze, vacuum on stand by dbs in pg_stat_user_tables it retu=
rns null. Will vacuum/ analyze do not replicate to stand by instances?? Do w=
e have to run separately on all the Stand by instances??<br>
<br>
The data changes will propagate, but those action counters are just<br>
maintained locally to the primary server.&nbsp; Their values on a hot<br>
standby are meaningless, probably always zero, because a standby<br>
*can't* change the data on its own.<br>
<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp; regards, tom lane<br>
<br>
<br>
</blockquote></div>
</div></blockquote></div></body></html>=

--Apple-Mail-9E8FF95A-790D-41DB-9083-A0345E9CBE0A--





view thread (4+ messages)

Message-ID: <22FA6562-087D-45F1-8813-9ACF4353417E@gmail.com>
Permalink:  ../22FA6562-087D-45F1-8813-9ACF4353417E@gmail.com/
Also on:    postgresql.org/message-id/22FA6562-087D-45F1-8813-9ACF4353417E@gmail.com

 · 

reply

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: teja.jakkidi05@gmail.com, obireddy.g1997@gmail.com, tgl@sss.pgh.pa.us, pgsql-admin@lists.postgresql.org
  Subject: Re: Vacuum and analyze for objects on physical stand by dbs
  In-Reply-To: <22FA6562-087D-45F1-8813-9ACF4353417E@gmail.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