Re: Controlling changes in plpgsql variable resolution

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Robert Haas" <robertmhaas(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, "Stephen Frost" <sfrost(at)snowman(dot)net>
Subject: Re: Controlling changes in plpgsql variable resolution
Date: 2009-10-19 17:05:10
Message-ID: 4ADC55F6020000250002BB1C@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"David E. Wheeler" <david(at)kineticode(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2009-10-19 17:07:40 Re: Scaling up deferred unique checks and the after trigger queue
Previous Message Robert Haas 2009-10-19 17:02:37 Re: Scaling up deferred unique checks and the after trigger queue