From: Jeff Davis <pgsql@j-davis.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@postgresql.org
Subject: Re: Possible to create a hidden collation
Date: Thu, 11 May 2023 17:27:04 -0700
Message-ID: <db17b95155e442515f8982cd3f8fa378841b006f.camel@j-davis.com> (raw)
In-Reply-To: <1209303.1683849734@sss.pgh.pa.us>
References: <051c9395cf880307865ee8b17acdbf7f838c1e39.camel@j-davis.com>
<1209303.1683849734@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: pgsql@j-davis.com, tgl@sss.pgh.pa.us
Subject: Re: Possible to create a hidden collation
In-Reply-To: <db17b95155e442515f8982cd3f8fa378841b006f.camel@j-davis.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox