Performance after restart/reboot pre-Analyze

From: David Fogarty <dfogarty(at)icsusa(dot)com>
To: pgsql-novice(at)lists(dot)postgresql(dot)org
Subject: Performance after restart/reboot pre-Analyze
Date: 2024-03-28 15:43:37
Message-ID: 6F39634B-20B1-4683-9320-C4D7B68D53CF@icsusa.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-novice


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

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message David G. Johnston 2024-03-28 15:50:53 Re: Performance after restart/reboot pre-Analyze
Previous Message Tom Lane 2024-03-14 19:17:12 Re: Sharp edge when dropping columns