Re: Bug in either collation docs or code - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Bug in either collation docs or code
Date
Msg-id CAKFQuwavMqRr=eXMFRWj5ER4BdvPcF-=o2a3p__MeWxWmCaCDw@mail.gmail.com
Whole thread Raw
In response to Re: Bug in either collation docs or code  (Melanie Plageman <melanieplageman@gmail.com>)
List pgsql-hackers
On Fri, Jun 8, 2018 at 9:24 AM, Melanie Plageman <melanieplageman@gmail.com> wrote:
It seems like this would not allow the function/operator to decide if it cares about a determinate collation during execution, since it would already have errored out during planning.

In the case where the function/operator doesn't care one shouldn't be attaching explicit collation clauses to its inputs anyway - it is a semantic bug if nothing else and a bug during planning pointing that out seems useful.

David J.

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: why partition pruning doesn't work?
Next
From: Tom Lane
Date:
Subject: Re: Transform for pl/perl