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

From Andres Freund
Subject Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Date
Msg-id A675BDE8-588C-4316-9DA4-4646E614128C@anarazel.de
Whole thread Raw
In response to Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres  (Peter Geoghegan <pg@heroku.com>)
Responses Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
List pgsql-bugs
On February 4, 2016 5:16:16 PM GMT+03:00, Peter Geoghegan <pg@heroku.com> wrote:
>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. Önder's complaint was
>that deparsing doesn't work. It was not that stored rules were ever
>independently broken.

I want the deparse output to be executed.

Andres

---
Please excuse brevity and formatting - I am writing this on my mobile phone.

pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Next
From: Federico Campoli
Date:
Subject: Re: BUG #13911: pg_upgrade from 8.4 to 9.5 broken