writes:
> On Sep 16, 2011, at 11:11 AM, Tom Lane wrote:
>> Hmm. It would require an extra catalog lookup per parameter to enforce
>> that. Not sure that it's worth it just to prevent "peculiar" errors.
>> Can you point to any worse consequences?
> I haven't found any more severe issues and I'll
On Sep 16, 2011, at 11:11 AM, Tom Lane wrote:
> "Caleb Welton" writes:
>> statements such as:
>> PREPARE p1(anyelement) AS SELECT quote_literal($1);
>> PREPARE p2(internal) AS SELECT int2recv($1);
>> Should not be allowed.
>
> Hmm. It would require an extra catalog lookup per parameter to en
"Caleb Welton" writes:
> statements such as:
> PREPARE p1(anyelement) AS SELECT quote_literal($1);
> PREPARE p2(internal) AS SELECT int2recv($1);
> Should not be allowed.
Hmm. It would require an extra catalog lookup per parameter to enforce
that. Not sure that it's worth it just to prevent
The following bug has been logged online:
Bug reference: 6212
Logged by: Caleb Welton
Email address: caleb.wel...@emc.com
PostgreSQL version: 9.0
Operating system: OSX
Description:PREPARE(pseudotype) should be blocked off
Details:
statements such as:
PREPARE p1(an
