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 20160204204908.ew45cz73rsjgyptd@alap3.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 2016-02-04 12:43:15 -0800, Peter Geoghegan wrote:
> 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. Ö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?

Seems fairly simple to write a DO statement that does something like
v_sql = pg_get_viewdef(viewname);
EXECUTE 'DROP VIEW '||viewname::regclass;
EXECUTE v_sql;
in a query over pg_views.

pgsql-bugs by date:

Previous
From: Peter Geoghegan
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