| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| 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:09:09 |
| Message-ID: | 20230217180909.oqxjgjudbsofn666@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2023-02-17 10:00:41 -0800, Jeff Davis wrote:
> 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.
-1. That's just going to cause pain one major version upgrade further down the
line. Why would we want to incur that pain?
> There's already a check that the new cluster is empty, so I think it's
> safe to hack the pg_database locale fields.
I don't think we need to, we do issue the CREATE DATABASEs. So we just need to
make sure that includes the collation provider info, and the proper template
database, in pg_upgrade mode.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-02-17 18:18:19 | Re: The output sql generated by pg_dump for a create function refers to a modified table name |
| Previous Message | Jeff Davis | 2023-02-17 18:00:41 | Re: Move defaults toward ICU in 16? |