Re: Explicit deterministic COLLATE fails with pattern matching operations on column with non-deterministic collation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: James Lucas <jlucasdba(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Explicit deterministic COLLATE fails with pattern matching operations on column with non-deterministic collation
Date: 2020-05-28 20:48:00
Message-ID: 7943.1590698880@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

James Lucas <jlucasdba(at)gmail(dot)com> writes:
> So that is something to be aware of - the collation defined on the
> column can impact stats values, which could in turn impact plans
> chosen for queries that use alternative collations.

Yeah. At some point we might try to collect stats with respect to
multiple collations, but that's a long way off probably.

(I have suggested that CREATE STATISTICS could be extended to
control this type of thing, but I don't think anyone's worked
on making it happen.)

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-05-29 00:50:48 BUG #16469: High unicode character mangled on write and read with ODBC driver
Previous Message James Lucas 2020-05-28 20:42:07 Re: Explicit deterministic COLLATE fails with pattern matching operations on column with non-deterministic collation