Date: Tue, 2 Jul 2024 09:51:45 -0700
From: Noah Misch <noah@leadboat.com>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Peter Eisentraut <peter@eisentraut.org>,
	Daniel Verite <daniel@manitou-mail.org>,
	Robert Haas <robertmhaas@gmail.com>,
	Jeremy Schneider <schneider@ardentperf.com>,
	pgsql-hackers@postgresql.org
Subject: Re: Built-in CTYPE provider
Message-ID: <20240702165145.af.nmisch@google.com>
References: <846a7e1fa2024918b58ff7583523a2f3de9a11b4.camel@j-davis.com>
 <3117d30aa911b408b90420f4f280fa0c3b5851be.camel@j-davis.com>
 <4135cf11-206d-40ed-96c0-9363c1232379@eisentraut.org>
 <7451f81ba0cb512222ab759de8ca1cffe44e9acb.camel@j-davis.com>
 <1f309153-8198-4efa-86dd-8c304ec0040c@eisentraut.org>
 <a21b515000f121244db2a5570d4292d19df23379.camel@j-davis.com>
 <20240629220857.fb.nmisch@google.com>
 <1ecfeb4d2b1b7f119fa917d3052a3aecfaf4f425.camel@j-davis.com>
 <20240701230352.2c.nmisch@google.com>
 <da7a19008c2b1f19b3f91b446fe09847512694f1.camel@j-davis.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <da7a19008c2b1f19b3f91b446fe09847512694f1.camel@j-davis.com>
User-Agent: Mutt/2.2.12 (2023-09-09)
Archived-At: 
 <https://www.postgresql.org/message-id/20240702165145.af.nmisch%40google.com>
Precedence: bulk

On Mon, Jul 01, 2024 at 06:19:08PM -0700, Jeff Davis wrote:
> On Mon, 2024-07-01 at 16:03 -0700, Noah Misch wrote:
> >   An alternative would be to make pg_upgrade reject
> > operating on a cluster that contains use of $SUBJECT.
> 
> That wouldn't help anyone.

Can you say more about that?  For the last decade at least, I think our
standard for new features has been to error rather than allow an operation
that creates a known path to wrong query results.  I think that's a helpful
standard that we should continue to follow.