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 21:09:43
Message-ID: CAM3SWZQoejSg5KB8pAFVUqci-uk7KmLJLFBWt=4EyvyB5W-ShA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Feb 4, 2016 at 12:49 PM, Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2016-02-04 21:15:34 Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Previous Message Andres Freund 2016-02-04 20:49:08 Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres