Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Geoghegan <pg(at)heroku(dot)com>, Ö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-07 20:08:32
Message-ID: D631DD5C-F703-4A5B-9B2B-F225E5F013D8@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On February 7, 2016 9:02:11 PM GMT+01:00, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Andres Freund <andres(at)anarazel(dot)de> writes:

>I think actually Andres' proposal wouldn't be all that helpful, because
>it would only detect deparse problems for constructs that happen to
>appear in views/rules that exist at the instant the test runs.

That's be fine for this purpose. This specific line had two hard to spot roots already...

---
Please excuse brevity and formatting - I am writing this on my mobile phone.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew Gierth 2016-02-07 23:21:57 Re: BUG #13863: Select from views gives wrong results
Previous Message Tom Lane 2016-02-07 20:02:11 Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres