pgsql: Coerce 'unknown' type parameters to the right type in the

From: heikki(at)postgresql(dot)org (Heikki Linnakangas)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Coerce 'unknown' type parameters to the right type in the
Date: 2010-08-18 12:20:15
Message-ID: 20100818122015.EE2B27541D7@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Log Message:
-----------
Coerce 'unknown' type parameters to the right type in the fixed-params
parse_analyze() function. That case occurs e.g with PL/pgSQL
EXECUTE ... USING 'stringconstant'.

The coercion with a CoerceViaIO node. The result is similar to the coercion
via input function performed for unknown constants in coerce_type(),
except that this happens at runtime.

Backpatch to 9.0. The issue is present in 8.4 as well, but the coerce param
hook infrastructure this patch relies on was introduced in 9.0. Given the
lack of user reports and harmlessness of the bug, it's not worth attempting
a different fix just for 8.4.

Modified Files:
--------------
pgsql/src/backend/parser:
parse_param.c (r2.4 -> r2.5)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_param.c?r1=2.4&r2=2.5)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-08-18 12:20:22 pgsql: Coerce 'unknown' type parameters to the right type in the
Previous Message User Fxjr 2010-08-18 03:19:58 npgsql - Npgsql2: Added fix to return CLR type when working with

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2010-08-18 12:45:49 Re: Progress indication prototype
Previous Message Pavel Stehule 2010-08-18 12:08:43 proposal: tuplestore, tuplesort aggregate functions