From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: TEXT vs VARCHAR join qual push down diffrence, bug or expected? |
Date: | 2015-09-24 16:52:11 |
Message-ID: | 12482.1443113531@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com> writes:
> On Wed, Sep 23, 2015 at 10:15 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> After a bit more thinking and experimentation, I propose the attached
>> patch.
> I had a look over the patch and reviewed it. It is in excellent state to
> check-in.
After further thought I decided that the base case for
Const/Param/non-foreign-Vars wasn't quite right either. If we don't like
the collation we should just set the state to UNSAFE not fail immediately,
because it might appear in a context where collation doesn't matter.
An example is "var IS NOT NULL".
So I've committed the attached modification of that patch.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
improve-postgres-fdw-collation-handling-2.patch | text/x-diff | 18.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2015-09-24 16:55:52 | Re: DBT-3 with SF=20 got failed |
Previous Message | Josh Berkus | 2015-09-24 16:43:19 | Re: multivariate statistics / patch v7 |