Re: proposal: change behavior on collation version mismatch - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: proposal: change behavior on collation version mismatch
Date
Msg-id eec6ecc8f25e698c7ab29b3384d190bd4a4a4485.camel@j-davis.com
Whole thread Raw
In response to Re: proposal: change behavior on collation version mismatch  (Jeremy Schneider <schnjere@amazon.com>)
List pgsql-hackers
On Mon, 2023-11-27 at 15:35 -0800, Jeremy Schneider wrote:

>  For many enterprise customers, if they ask why their database
> wouldn't accept connections after an OS upgrade and we explained that
> durability & correctness is prioritized over availability, I think
> they would agree we're doing the right thing.

They may agree, but their database is still down, and they'll be
looking for a clear process to get it going again, ideally within their
maintenance window.

It would be really nice to agree on such a process, or even better, to
implement it in code.

> After some years of ICU and PG, I'm just coming to a conclusion that
> the right thing to do is stay safe and don't change ICU versions (or
> glibc versions) for existing databases in-place.

I don't disagree, but for a lot of users that depend on their operating
system and packaging infrastructure, that is not very practical.

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: SSL tests fail on OpenSSL v3.2.0
Next
From: shveta malik
Date:
Subject: Re: Synchronizing slots from primary to standby