Skip site navigation (1) Skip section navigation (2)

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Coerce 'unknown' type parameters to the right type in the
Date: 2010-08-18 13:57:19
Message-ID: 19030.1282139839@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
heikki(at)postgresql(dot)org (Heikki Linnakangas) writes:
> 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.

Unfortunately, this entirely fails to enforce the rule that an unknown
Param be coerced the same way everywhere.  You'd need a cleanup pass as
well, cf check_variable_parameters().

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Pavel StehuleDate: 2010-08-18 14:03:25
Subject: Re: proposal: tuplestore, tuplesort aggregate functions
Previous:From: Tom LaneDate: 2010-08-18 13:53:24
Subject: Re: proposal: tuplestore, tuplesort aggregate functions

pgsql-committers by date

Next:From: Heikki LinnakangasDate: 2010-08-18 15:03:34
Subject: Re: pgsql: Coerce 'unknown' type parameters to the right type in the
Previous:From: Heikki LinnakangasDate: 2010-08-18 12:20:22
Subject: pgsql: Coerce 'unknown' type parameters to the right type in the

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group