Re: [Sender Address Forgery]Re: [HACKERS] path toward fasterpartition pruning - Mailing list pgsql-hackers

From David Rowley
Subject Re: [Sender Address Forgery]Re: [HACKERS] path toward fasterpartition pruning
Date
Msg-id CAKJS1f8LyED__o3va2b-eEcSrX7rOmVwAhVU0VgqDsQDRo=DMA@mail.gmail.com
Whole thread Raw
In response to Re: [Sender Address Forgery]Re: [HACKERS] path toward fasterpartition pruning  (David Rowley <david.rowley@2ndquadrant.com>)
List pgsql-hackers
> On 11 January 2018 at 22:52, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> wrote:
>> Can you point me to the email where Beena reported the problem in question?
>
> https://www.postgresql.org/message-id/CAOG9ApERiop7P=GRkqQKa82AuBKjxN3qVixie3WK4WqQpEjS6g@mail.gmail.com

To save you from having to look at the run-time prune patch, here's
case that break in v18.

create table xy (a int, b text) partition by range (a,b);
create table xy1 partition of xy for values from (0,'a') to (10, 'b');
select * from xy where a = 1 and b in('x','y');
ERROR:  operator 531 is not a member of opfamily 1976

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: [Sender Address Forgery]Re: [HACKERS] path toward fasterpartition pruning
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] Planning counters in pg_stat_statements