Feedback-ID: i76984098:Fastmail
Message-ID: <3ca42bdd-1753-4870-bad7-e4f05214c423@aklaver.com>
Date: Thu, 23 May 2024 07:45:08 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Restore of a reference database kills the auto analyze
 processing.
To: HORDER Philip <Phil.Horder@uk.thalesgroup.com>,
 "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
References: <b1a1d01482574d758d88e8d6ac2a4342@uk.thalesgroup.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <b1a1d01482574d758d88e8d6ac2a4342@uk.thalesgroup.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/3ca42bdd-1753-4870-bad7-e4f05214c423%40aklaver.com>
Precedence: bulk

On 5/23/24 06:01, HORDER Philip wrote:
> Classified as: {OPEN}
> 
> I actually hadn't thought to look for Postgres bugs, the system is so reliable for us, it just doesn't go wrong!
> 
> I can trigger the fault be running a reload of the lfm database, and we've been running Postgres 10 & 13 for several years now without seeing this problem.
> 
> Our symptoms match that bug description exactly, so I'm pretty confident this is the problem.
> I'll have to push through the right paperwork to get a Postgres update, and that will take a while

While you are doing the paperwork make sure it is for upgrade to 15.7. 
Also might mention minor upgrades (x in X.x) are a good idea as 
Postgres, like any software, does get bugs and the minor releases fix 
them. Point the folks in charge at:

https://www.postgresql.org/docs/15/release.html

Also minor releases as a rule do not require dump/restore or pg_upgrade 
or other heavy lifting. There have been exceptions, but they are rare.

> 
> Thank you so much for your time.
> 
> Phil Horder
> Database Mechanic
> 
> Thales
> Land & Air Systems
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com