| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Support partition pruning at execution time |
| Date: | 2018-04-17 19:26:49 |
| Message-ID: | 20180417192649.kuwcdv7btvdo2iuq@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
David Rowley wrote:
> I've made another pass over the nodeAppend.c code and I'm unable to
> see what might cause this, although I did discover a bug where
> first_partial_plan is not set taking into account that some subplans
> may have been pruned away during executor init. The only thing I think
> this would cause is for parallel workers to not properly help out with
> some partial plans if some earlier subplans were pruned. I can see no
> reason for this to have caused this particular issue since the
> first_partial_plan would be 0 with and without the attached fix.
Pushed this.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2018-04-17 20:11:10 | pgsql: Fix confusion on the padding of GIDs in on commit and abort reco |
| Previous Message | Alvaro Herrera | 2018-04-17 19:26:13 | pgsql: Update Append's idea of first_partial_plan |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Banck | 2018-04-17 19:43:47 | Re: Gotchas about pg_verify_checksums |
| Previous Message | Andres Freund | 2018-04-17 19:12:26 | Re: reloption to prevent VACUUM from truncating empty pages at the end of relation |