Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Дата
Msg-id CAM3SWZTYhyxDFp_=hz052+vosgRhNOWmzs7SoGW-krmbW4998Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres  (Andres Freund <andres@anarazel.de>)
Ответы Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Список pgsql-bugs
On Thu, Feb 4, 2016 at 4:11 AM, Andres Freund <andres@anarazel.de> wrote:
> Can you add code to execute the resulting statements? Because obviously
> just seeing the output ain't enough. Seems like an easily repeatable
> error, and the regression test scase ought to be pretty easy with a DO
> and a loop.

What do you mean?

The stored rules whose output was modified as part of the fix are
actually executed already -- no change there. =C3=96nder's complaint was
that deparsing doesn't work. It was not that stored rules were ever
independently broken.

--=20
Peter Geoghegan

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres