| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GatherMerge misses to push target list |
| Date: | 2017-09-12 02:31:47 |
| Message-ID: | CAA4eK1JAZMLtEL7JVO3AyxX9_PGc4PDwE13q3MFhwYuJ_HYM=g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 6, 2017 at 10:04 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> During my recent work on costing of parallel paths [1], I noticed that
> we are missing to push target list below GatherMerge in some simple
> cases like below.
>
I think this should be considered as a bug-fix for 10.0, but it
doesn't block any functionality or give wrong results, so we might
consider it as an optimization for GatherMerge. In any case, I have
added this to next CF.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2017-09-12 03:14:44 | Re: Re: proposal - using names as primary names of plpgsql function parameters instead $ based names |
| Previous Message | Michael Paquier | 2017-09-12 02:28:44 | Re: [Proposal] Allow users to specify multiple tables in VACUUM commands |