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

From: Andres Freund <andres(at)anarazel(dot)de>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Önder Kalacı <onderkalaci(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Date: 2016-02-04 15:15:14
Message-ID: A675BDE8-588C-4316-9DA4-4646E614128C@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On February 4, 2016 5:16:16 PM GMT+03:00, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>On Thu, Feb 4, 2016 at 4:11 AM, Andres Freund <andres(at)anarazel(dot)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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2016-02-04 15:38:28 Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby
Previous Message Peter Geoghegan 2016-02-04 14:18:05 Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres