Re: New CORRESPONDING clause design
От | Pavel Stehule |
---|---|
Тема | Re: New CORRESPONDING clause design |
Дата | |
Msg-id | CAFj8pRBNjgkCuPJTiQ87Lb-EZjT=w5s21rT4P=Gk3aKFmCiX-A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: New CORRESPONDING clause design (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: New CORRESPONDING clause design
|
Список | pgsql-hackers |
2017-03-28 14:18 GMT+02:00 Pavel Stehule <pavel.stehule@gmail.com>:
2017-03-28 13:58 GMT+02:00 Surafel Temesgen <surafel3000@gmail.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
maybe some recheck after analyze stage to remove invalid columns can be good enough.
Regards
Pavel
RegardsPavelOn Mon, Mar 27, 2017 at 11:48 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:Hifresh 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 onSELECT 0 AS x1, 1 AS a, 0 AS x2, 2 AS b, 0 AS x3, -1 AS x3UNION ALL CORRESPONDING SELECT 4 AS b, 0 AS x4, 3 AS a, 0 AS x6, -1 AS x6UNION ALL CORRESPONDING SELECT 0 AS x8, 6 AS b, -100 AS x9;I'll mark this patch as waiting on authorRegardsPavel
В списке pgsql-hackers по дате отправления: