Postgres Pro
Downloads
Home   >   mailing lists

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 CAM3SWZQoejSg5KB8pAFVUqci-uk7KmLJLFBWt=4EyvyB5W-ShA@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
Tree view 
On Thu, Feb 4, 2016 at 12:49 PM, Andres Freund <andres@anarazel.de> wrote:
> 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.

Sorry, I still don't get it. How does that help with ON CONFLICT
arbiter WHERE clause deparsing?


--
Peter Geoghegan

pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Next
From: Andres Freund
Date:
Subject: Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres