Re: Internal error XX000 with enable_partition_pruning=on, pg 11 beta1 on Debian - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Internal error XX000 with enable_partition_pruning=on, pg 11 beta1 on Debian
Date
Msg-id 18306.1533167304@sss.pgh.pa.us
Whole thread Raw
In response to Re: Internal error XX000 with enable_partition_pruning=on, pg 11beta1 on Debian  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: Internal error XX000 with enable_partition_pruning=on, pg 11beta1 on Debian
Re: Internal error XX000 with enable_partition_pruning=on, pg 11beta1 on Debian
List pgsql-hackers
David Rowley <david.rowley@2ndquadrant.com> writes:
> On 20 July 2018 at 01:03, David Rowley <david.rowley@2ndquadrant.com> wrote:
>> I've attached a patch intended for master which is just v2 based on
>> post 5220bb7533.

I've pushed the v3 patch with a lot of editorial work (e.g. cleaning
up comments you hadn't).  I still want to think about getting rid of
some of the "extraneous" bitmapsets and lists that are running around
here ... but time grows short before beta3, and it's not clear that
that would be appropriate material to push into v11 anyway.

> In [1] I mentioned that I think that bug should be fixed as part of
> this bug fix too.

I didn't include this change because (a) it's late, (b) no test
case was included, and (c) I don't entirely believe it anyway.
How would a rel be both leaf and nonleaf?  Isn't this indicative
of a problem somewhere upstream in the planner?

            regards, tom lane


pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Making "COPY partitioned_table FROM" faster
Next
From: Andrew Gierth
Date:
Subject: Problems with plan estimates in postgres_fdw