| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New CORRESPONDING clause design |
| Date: | 2017-03-28 12:18:04 |
| Message-ID: | CAFj8pRCDwqScv3qgAjHNzfX3oViA50WgdMEAMs_94C-OGE8JXw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2017-03-28 13:58 GMT+02:00 Surafel Temesgen <surafel3000(at)gmail(dot)com>:
> can you help with fixing it Pavel?
>
There must be some new preanalyze stage - you have to know result columns
before you are starting a analyze
Regards
Pavel
>
> On Mon, Mar 27, 2017 at 11:48 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
>
>> Hi
>>
>> fresh update - I enhanced Value node by location field as Tom proposal.
>>
>> Few more regress tests.
>>
>> But I found significant issue, that needs bigger fix - Surafel, please,
>> can you fix it.
>>
>> It crash on
>>
>> SELECT 0 AS x1, 1 AS a, 0 AS x2, 2 AS b, 0 AS x3, -1 AS x3
>> UNION ALL CORRESPONDING SELECT 4 AS b, 0 AS x4, 3 AS a, 0 AS x6, -1 AS x6
>> UNION ALL CORRESPONDING SELECT 0 AS x8, 6 AS b, -100 AS x9;
>>
>> I'll mark this patch as waiting on author
>>
>> Regards
>>
>> Pavel
>>
>>
>>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-03-28 13:03:26 | Re: [COMMITTERS] pgsql: Clean up Perl code according to perlcritic |
| Previous Message | Surafel Temesgen | 2017-03-28 11:58:52 | Re: New CORRESPONDING clause design |