Re: pgsql: Try again to fix the way the scanjoin_target is used with partia - Mailing list pgsql-committers

From Amit Kapila
Subject Re: pgsql: Try again to fix the way the scanjoin_target is used with partia
Date
Msg-id CAA4eK1JX8Wc0pKqn6SmhEWm2GdZE-E2wmLv+tHRbY+m-tK7tDw@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Try again to fix the way the scanjoin_target is used with partia  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: pgsql: Try again to fix the way the scanjoin_target is used with partia  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On Sat, Jun 18, 2016 at 7:44 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Sat, Jun 18, 2016 at 7:06 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >
> > Amit Kapila <amit.kapila16@gmail.com> writes:
> > > On Sat, Jun 18, 2016 at 6:11 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > >> Was this supposed to fix the "ORDER/GROUP BY expression not found in
> > >> targetlist" problem?
> > >> If so, it hasn't ...
> >
> > > Can you please share why you think so?
> >
> > Run the regression tests with the settings mentioned in
> > https://www.postgresql.org/message-id/22782.1466100870@sss.pgh.pa.us
> >
> > You'll get a lot of cosmetic diffs (parallelized plans in EXPLAIN
> > and/or varying output row orders), but also half a dozen of the
> > aforesaid failure.
> >
>
> I think I got the reason of those failures.

Patch fixing the failures along with a new test case is attached with this mail


With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
Attachment

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix parallel-safety markings for contrib/dblink.
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Try again to fix the way the scanjoin_target is used with partia