From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: FailedAssertion on partprune |
Date: | 2018-08-29 17:38:57 |
Message-ID: | CA+TgmoaiFvO_C+APsRom4Y09gfS9Qc3Mq_bRWJgHoc=z5at01w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 27, 2018 at 6:05 PM, Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
> On behalf of the RMT, I just want to make sure this keeps moving along.
> It sounds like the next step is for Robert to verify that [3] is the
> expected
> behavior and then David can decide what to do from there.
Yes, that's the expected behavior. If we didn't regenerate the paths
there, we'd end up with
Result
-> Append
-> [various paths that produce a tlist which needs to be adjusted
later by the result node]
Instead of:
Append
-> [various paths that produce an adjusted tlist]
Paths of the former kind have already been generated; we regenerate
paths here to get the latter kind as well, which end up displacing the
old ones on cost.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2018-08-29 17:45:44 | Re: Removing useless \. at the end of copy in pgbench |
Previous Message | Tom Lane | 2018-08-29 16:56:07 | Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes |