| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Önder Kalacı <onderkalaci(at)gmail(dot)com> |
| Cc: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres |
| Date: | 2016-02-04 12:02:04 |
| Message-ID: | CAM3SWZSNiq6Eo_Y76LfQuYJmQdkvnz0nDvWQ2=XNeRi6wMPvSw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Jan 27, 2016 at 5:42 AM, Önder Kalacı <onderkalaci(at)gmail(dot)com> wrote:
> We use postgres' ruleutils.c to build SQL strings. I realized this while I
> was playing with UPSERTs on 9.5.
Here is a bug fix patch.
InferenceElem already had appropriate handling for this case.
Unfortunately, that did no help with the arbiter WHERE clause, since
it does not use InferenceElem. I haven't moved the existing handling;
I feel it makes sense to do this separately for each case.
Thanks for the report!
--
Peter Geoghegan
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Fix-arbiter-WHERE-clause-deparsing.patch | text/x-patch | 3.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-02-04 12:11:41 | Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres |
| Previous Message | reiner.peterke | 2016-02-04 09:40:43 | BUG #13916: Only the install user can be defined in the new cluster |