From: David Fogarty <dfogarty@icsusa.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_D73758C6-7D86-421B-B6DD-82011F630366"
Reply-To: David Fogarty <dfogarty@icsusa.com>
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Subject: Performance after restart/reboot pre-Analyze
Message-Id: <6F39634B-20B1-4683-9320-C4D7B68D53CF@icsusa.com>
Date: Thu, 28 Mar 2024 10:43:37 -0500
To: pgsql-novice@lists.postgresql.org
Archived-At: 
 <https://www.postgresql.org/message-id/6F39634B-20B1-4683-9320-C4D7B68D53CF%40icsusa.com>
Precedence: bulk


--Apple-Mail=_D73758C6-7D86-421B-B6DD-82011F630366
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


Hello,

It seems like whenever I restart my database server performance is quite =
bad until an Analyze has been performed. I expect this is due to the =
query planner needing new stats, but that leads me to three questions:

1. Is there a way to have Analyze stats/query planner "plans" persist =
through a restart? Like store them somehow after an Analyze and tell =
Postgres where to pull them from?

2. If not, is there a technical reason/limitation as to why?

3. Are there general configuration settings/optimizations for improving =
performance after a restart before an Analyze has finished?

If this would be better directed toward a different mailing list, let me =
know. I appreciate any guidance on this.
Also, if it affects anything, the environments are on AWS RDS, we're =
currently on 14 and 15 but will be upgrading to 16 very soon. I've only =
recently been brought into this, so I'm not fully aware of what kinds of =
queries we mostly handle or how the various tables/views are indexed.

Thanks,
Dave


--Apple-Mail=_D73758C6-7D86-421B-B6DD-82011F630366
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;"><div><br>
</div>
Hello,<div><br></div><div>It seems like whenever I restart my database =
server performance is quite bad until an Analyze has been performed. I =
expect this is due to the query planner needing new stats, but that =
leads me to three questions:</div><div><br></div><div>1. Is there a way =
to have Analyze stats/query planner "plans" persist through a restart? =
Like store them somehow after an Analyze and tell Postgres where to pull =
them from?</div><div><br></div><div>2. If not, is there a technical =
reason/limitation as to why?</div><div><br></div><div>3. Are there =
general configuration settings/optimizations for improving performance =
after a restart before an Analyze has =
finished?</div><div><br></div><div>If this would be better directed =
toward a different mailing list, let me know. I appreciate any guidance =
on this.</div><div>Also, if it affects anything, the environments are on =
AWS RDS, we're currently on 14 and 15 but will be upgrading to 16 very =
soon. I've only recently been brought into this, so I'm not fully aware =
of what kinds of queries we mostly handle or how the various =
tables/views are =
indexed.</div><div><br></div><div>Thanks,</div><div>Dave</div><div><br></d=
iv></body></html>=

--Apple-Mail=_D73758C6-7D86-421B-B6DD-82011F630366--