On Sat, Jun 18, 2016 at 7:44 AM, Amit Kapila <amit.kapil...@gmail.com> wrote: > > On Sat, Jun 18, 2016 at 7:06 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > > > > Amit Kapila <amit.kapil...@gmail.com> writes: > > > On Sat, Jun 18, 2016 at 6:11 AM, Tom Lane <t...@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.1466100...@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
fix_scanjoin_pathtarget_v4.patch
Description: Binary data
-- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
