Re: Why do indexes and sorts use the database collation?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Why do indexes and sorts use the database collation?
Date: 2023-11-14 19:47:42
Message-ID: 2516190.1699991262@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> On Tue, 2023-11-14 at 17:15 +0100, Peter Eisentraut wrote:
>> The problem is that the user has no way to declare whether they just
>> want this.

> We should add a way to declare that a primary key should create an
> index in a particular collation.

Why should that ever be different from the column's own declared
collation?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-11-14 20:01:47 Re: pgsql: doc: fix wording describing the checkpoint_flush_after GUC
Previous Message Tom Lane 2023-11-14 19:46:21 Re: Implement missing join selectivity estimation for range types