From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Davis <pgsql@j-davis.com>
Cc: pgsql-bugs@postgresql.org
Subject: Re: Possible to create a hidden collation
Date: Thu, 11 May 2023 20:02:14 -0400
Message-ID: <1209303.1683849734@sss.pgh.pa.us> (raw)
In-Reply-To: <051c9395cf880307865ee8b17acdbf7f838c1e39.camel@j-davis.com>
References: <051c9395cf880307865ee8b17acdbf7f838c1e39.camel@j-davis.com>
Jeff Davis <pgsql@j-davis.com> writes:
> There's no reason to create user defined collations with collencoding=-
> 1. As far as I can tell, collencoding is only there to hide built-in
> collations (inherited from template0) that aren't compatible with the
> current database encoding. So we can just always create user-defined
> collations with collencoding=GetDatabaseEncoding().
What happens if somebody makes a user-defined collation in template0
and then clones that into a different encoding? I guess the user-defined
collation would then be hidden/inaccessible in the clone DB, so maybe it's
fine.
regards, tom lane
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: tgl@sss.pgh.pa.us, pgsql@j-davis.com
Subject: Re: Possible to create a hidden collation
In-Reply-To: <1209303.1683849734@sss.pgh.pa.us>
* 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