Re: Controlling changes in plpgsql variable resolution - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Controlling changes in plpgsql variable resolution
Date
Msg-id 4ADC55F6020000250002BB1C@gw.wicourts.gov
Whole thread Raw
In response to Re: Controlling changes in plpgsql variable resolution  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: Controlling changes in plpgsql variable resolution
List pgsql-hackers
"David E. Wheeler" <david@kineticode.com> wrote:
> I'd be in favor of a GUC that I could turn on to throw an error
> when there's an ambiguity.
I would consider hiding one definition with another very bad form, so
I would prefer to have plpgsql throw an error when that happens.  I
don't particularly care whether that is the only supported behavior or
whether there's a GUC to control it, or what its default is, if
present.
-Kevin


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Scaling up deferred unique checks and the after trigger queue
Next
From: Dean Rasheed
Date:
Subject: Re: Scaling up deferred unique checks and the after trigger queue