Re: Collatability of type "name"

On Mon, Dec 10, 2018 at 2:50 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I feel like #2 is probably really the Right Thing,

I think so, too.

> Also, I think that either solution would lead to some subtle changes
> in semantics. For example, right now if you compare a name column
> to a text value, you get a text (collation-aware) comparison using
> the database's default collation. It looks like if name columns
> are marked with attcollation = 'C', that would win and the comparison
> would now have 'C' collation unless you explicitly override it with
> a COLLATE clause. I'm not sure this is a bad thing --- it'd be more
> likely to match the sort order of the index on the column --- but it
> could surprise people.

It's not great to change the semantics of stuff like this, but it
doesn't sound all that bad.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company