From: Tom Lane <tgl@sss.pgh.pa.us>
To: James Lucas <jlucasdba@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: Explicit deterministic COLLATE fails with pattern matching operations on column with non-deterministic collation
Date: Thu, 28 May 2020 16:48:00 -0400
Message-ID: <7943.1590698880@sss.pgh.pa.us> (raw)
In-Reply-To: <CAAFmbbOez_LbhD767pPH0LGdEF3=nP9CdtmU+7gYxF_f-_Ce0w@mail.gmail.com>
References: <7417.1590690568@sss.pgh.pa.us>
<6351fb21-8282-406c-af64-22a3c9e1219b@manitou-mail.org>
<CAAFmbbOez_LbhD767pPH0LGdEF3=nP9CdtmU+7gYxF_f-_Ce0w@mail.gmail.com>
James Lucas <jlucasdba@gmail.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
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, jlucasdba@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Explicit deterministic COLLATE fails with pattern matching operations on column with non-deterministic collation
In-Reply-To: <7943.1590698880@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