| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-08-18 15:03:34 | Re: pgsql: Coerce 'unknown' type parameters to the right type in the |
| Previous Message | Heikki Linnakangas | 2010-08-18 12:20:22 | pgsql: Coerce 'unknown' type parameters to the right type in the |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2010-08-18 14:03:25 | Re: proposal: tuplestore, tuplesort aggregate functions |
| Previous Message | Tom Lane | 2010-08-18 13:53:24 | Re: proposal: tuplestore, tuplesort aggregate functions |