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

Re: RFD: Don't force plpgsql IN parameters to constant

From: Steve Prentice <prentice(at)cisco(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: RFD: Don't force plpgsql IN parameters to constant
Date: 2009-07-30 01:05:17
Message-ID: E0C44496-8477-4378-AD3B-678D1D2CB914@cisco.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Jul 29, 2009, at 5:26 PM, Robert Haas wrote:
> Wow.  I can imagine about a thousand ways that this could break
> existing applications.  I would not be prepared to bet a dollar that
> anything I've written would survive the impact unscathed.
>
> I have a feeling someone else is going to shoot you out of the water
> completely, but all I'll say is it would definitely need to be
> OPTIONAL.

I guess I don't get how it would break existing applications. All of  
the regression tests pass. The parameters are passed as a copy, so it  
can't modify your variable that you pass in. Perhaps I'm missing  
something--can you elaborate on how this would break existing  
applications?

-Steve

In response to

Responses

pgsql-hackers by date

Next:From: Steve PrenticeDate: 2009-07-30 01:06:41
Subject: Re: RFD: Don't force plpgsql IN parameters to constant
Previous:From: Robert HaasDate: 2009-07-30 00:42:53
Subject: Re: improvements for dict_xsyn extended synonym dictionary - RRR

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