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 20:49:08 |
Message-ID: | 20160204204908.ew45cz73rsjgyptd@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(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?
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2016-02-04 21:09:43 | Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres |
Previous Message | Peter Geoghegan | 2016-02-04 20:43:15 | Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres |