Re: plpgsql.warn_shadow

From: Joel Jacobson <joel(at)trustly(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marko Tiikkaja <marko(at)joh(dot)to>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpgsql.warn_shadow
Date: 2014-03-04 20:40:11
Message-ID: CAASwCXcv56Jg3nDBMTphJTQgQedRrEc_zQQtVxK2081KBpAeGw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 4, 2014 at 8:04 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> Lots of code quite correctly relies on this,
> including some I have written.

I really cannot see when it would be a good coding practise to do so,
there must be something I don't understand, I would greatly appreciate
if you can give a real-life example of such a PL/pgSQL function.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-03-04 20:50:18 Re: Custom Scan APIs (Re: Custom Plan node)
Previous Message Fabrízio de Royes Mello 2014-03-04 20:33:50 GSoC propostal - "CREATE SCHEMA ... LIKE ..."