Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Date
Msg-id CAM3SWZTYhyxDFp_=hz052+vosgRhNOWmzs7SoGW-krmbW4998Q@mail.gmail.com
Whole thread Raw
In response to Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres  (Andres Freund <andres@anarazel.de>)
Responses Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
List 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 by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Next
From: Peter Geoghegan
Date:
Subject: Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres