Re: expression evaluation with expected datatypes - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: expression evaluation with expected datatypes
Date
Msg-id 1341932624-sup-3455@alvh.no-ip.org
Whole thread Raw
In response to Re: expression evaluation with expected datatypes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: expression evaluation with expected datatypes
List pgsql-hackers
Excerpts from Tom Lane's message of mar jul 10 10:56:50 -0400 2012:
> Pavel Stehule <pavel.stehule@gmail.com> writes:
> > 2012/7/10 Dimitri Fontaine <dimitri@2ndquadrant.fr>:
> >> I'm not sure I can understand the difference between that and the use
> >> case for which you want to implement DO blocks with parameters.
>
> > this is similar to temporary functions - you need some temporary name
> > - it is insert to pg_proc, and you have to solve possible conflicts.
>
> What's to solve?  Presumably the WITH function name would take
> precedence over anything in the catalogs, the same as WITH query names
> take precedence over actual tables.

Hm, would the newly defined function mask all regular functions with
that name?  If not, a seemingly innocuous change in a query could mean
calling not the function defined in the WITH FUNCTION clause but another
one with the same name but different parameter count/types.

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Josh Kupershmidt
Date:
Subject: Re: [PATCH] psql \n shortcut for set search_path =
Next
From: Greg Stark
Date:
Subject: Re: Re: Allow replacement of bloated primary key indexes without foreign key rebuilds