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 D631DD5C-F703-4A5B-9B2B-F225E5F013D8@anarazel.de
Whole thread Raw
In response to Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On February 7, 2016 9:02:11 PM GMT+01:00, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>Andres Freund <andres@anarazel.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.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Next
From: Andrew Gierth
Date:
Subject: Re: BUG #13863: Select from views gives wrong results