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 CAM3SWZTDkXGR_QcaM5Q6TfuENWd1-7WQvo84n+7JhGL8EBa9vg@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
List pgsql-bugs
On Thu, Feb 4, 2016 at 7:15 AM, Andres Freund <andres@anarazel.de> wrote:
>>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.
>
> 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?


--=20
Peter Geoghegan

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #13911: pg_upgrade from 8.4 to 9.5 broken
Next
From: Andres Freund
Date:
Subject: Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres