Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
Date
Msg-id CAM3SWZSNiq6Eo_Y76LfQuYJmQdkvnz0nDvWQ2=XNeRi6wMPvSw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres  (Önder Kalacı <onderkalaci@gmail.com>)
Responses Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres
List pgsql-bugs
On Wed, Jan 27, 2016 at 5:42 AM, Önder Kalacı <onderkalaci@gmail.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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Parallel pg_restore fails to import views with triggers (dependency problem?)
Next
From: Andres Freund
Date:
Subject: Re: BUG #13891: Deparsed arbiter WHERE clauses cannot be parsed by Postgres