On Fri, Jan 13, 2017 at 7:13 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Dilip Kumar <dilipbal...@gmail.com> writes:
>> ERROR:  did not find '}' at end of input node at character 762

I could reproduce this error with simple query like:
SELECT * FROM information_schema.role_usage_grants WHERE object_type
LIKE 'FOREIGN%' AND object_name IN ('s6', 'foo') ORDER BY 1, 2, 3, 4,

The reason is that the stored rules have the old structure of Param.  See below:
{RELABELTYPE :arg {PARAM :paramkind 2 :paramid 1 :paramtype 11975
:paramtypmod -1 :paramcollid 100 :location -1}

The new variable parallel_safe is not present in above node.  If you
recreate the fresh database you won't see the above problem.  I have
observed a problem in equal function which I have fixed in the
attached patch.  I have also added a test, so that we can catch any
problem similar to what you have reported.

> I've not looked at the patches, but just seeing this error message,
> this looks like somebody's fat-fingered the correspondence between
> outfuncs.c and readfuncs.c processing.

I think what we need is catversion bump as Param is part of stored rules.

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

Attachment: pq_pushdown_correl_subplan_v2.patch
Description: Binary data

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to