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

From: Önder Kalacı <onderkalaci(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Date: 2016-01-27 13:42:58
Message-ID: CACawEhW1nBgeNn1r3hGgdyrJjbmaprrSGJdcQFpL-+Wj5C6JxA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Peter,

Thanks for the quick response.

> I'm curious: How did you find this bug? Did you just stumble upon it?
>
> We use postgres' ruleutils.c to build SQL strings. I realized this while I
was playing with UPSERTs on 9.5.

Does the rewritten query actually error? In other words, is your
> complaint strictly that deparsing is broken?

Yes, the rewritten query actually errors and our complaint is that a
deparsed query cannot be parsed by postgres again.

Thanks

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message otheus uibk 2016-01-27 14:49:22 Re: << unrecognized configuration parameter "pg_stat_statements.track" >>
Previous Message Andres Freund 2016-01-27 13:07:45 Re: << unrecognized configuration parameter "pg_stat_statements.track" >>