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

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
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 20:43:15
Message-ID: CAM3SWZTDkXGR_QcaM5Q6TfuENWd1-7WQvo84n+7JhGL8EBa9vg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Feb 4, 2016 at 7:15 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>>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.

That seems like something requiring an additional infrastructure. It
would be somewhat useful to smoke test lots of things like this. What
exactly do you have in mind?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2016-02-04 20:49:08 Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Previous Message Tom Lane 2016-02-04 18:32:12 Re: BUG #13911: pg_upgrade from 8.4 to 9.5 broken