| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Possible to create a hidden collation |
| Date: | 2023-05-12 00:27:04 |
| Message-ID: | db17b95155e442515f8982cd3f8fa378841b006f.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, 2023-05-11 at 20:02 -0400, Tom Lane wrote:
> What happens if somebody makes a user-defined collation in template0
> and then clones that into a different encoding?
I didn't know changing template0 was supported behavior for normal
operation.
> I guess the user-defined
> collation would then be hidden/inaccessible in the clone DB, so maybe
> it's
> fine.
Assuming we do support changes to template0, the fix would prevent
users from making a new ICU collation in template0 that is visible to
all encodings, other than calling pg_import_system_collations(). That
doesn't sound like a big problem; it's already impossible to do that
with libc collations.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2023-05-12 06:11:39 | BUG #17929: LLVMBuildGEP: symbol not found |
| Previous Message | Tom Lane | 2023-05-12 00:02:14 | Re: Possible to create a hidden collation |