| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Robert Haas <rhaas(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Try again to fix the way the scanjoin_target is used with partia |
| Date: | 2016-06-18 01:36:53 |
| Message-ID: | 27684.1466213813@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> writes:
> On Sat, Jun 18, 2016 at 6:11 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-06-18 01:44:46 | pgsql: Fix handling of argument and result datatypes for partial aggreg |
| Previous Message | Amit Kapila | 2016-06-18 01:29:47 | Re: pgsql: Try again to fix the way the scanjoin_target is used with partia |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2016-06-18 02:14:49 | Re: pgsql: Try again to fix the way the scanjoin_target is used with partia |
| Previous Message | Amit Kapila | 2016-06-18 01:29:47 | Re: pgsql: Try again to fix the way the scanjoin_target is used with partia |