| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Move defaults toward ICU in 16? |
| Date: | 2023-02-17 18:00:41 |
| Message-ID: | c412488b2a19467e4c037ad02db5d91431bdf178.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2023-02-17 at 09:05 -0800, Andres Freund wrote:
> > Thinking about this more, it's not clear to me if this would be in
> > scope for pg_upgrade or not.
>
> I don't think we should consider changing the default collation
> provider
> without making this more seamless, one way or another.
I guess I'm fine hacking pg_upgrade, but I think I'd like to make it
conditional on this specific case: only perform the fixup if the old
cluster is 15 or earlier and using libc and the newer cluster is 16 or
later and using icu.
There's already a check that the new cluster is empty, so I think it's
safe to hack the pg_database locale fields.
Regards,
Jeff Davis
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-02-17 18:09:09 | Re: Move defaults toward ICU in 16? |
| Previous Message | Andres Freund | 2023-02-17 17:52:01 | Re: Reducing System Allocator Thrashing of ExecutorState to Alleviate FDW-related Performance Degradations |