| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Daniel Verite <daniel(at)manitou-mail(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeremy Schneider <schneider(at)ardentperf(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Built-in CTYPE provider |
| Date: | 2024-07-02 22:05:09 |
| Message-ID: | 1200e97b-3a52-43c6-8b16-20cf45f58249@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02.07.24 18:51, Noah Misch wrote:
> 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.
I don't think the builtin locale provider is any different in this
respect from the other providers: The locale data might change and
there is a version mechanism to track that. We don't prevent pg_upgrade
in scenarios like that for other providers.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2024-07-02 22:59:49 | Re: collect_corrupt_items_vacuum.patch |
| Previous Message | Peter Eisentraut | 2024-07-02 21:51:37 | Re: Underscore in positional parameters? |