| From: | Florian Pflug <fgp(at)phlo(dot)org> |
|---|---|
| To: | Marko Tiikkaja <marko(at)joh(dot)to> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plpgsql.warn_shadow |
| Date: | 2014-01-15 06:07:12 |
| Message-ID: | 26FF16E2-A999-4397-8A82-8BDAC60DB9A4@phlo.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jan15, 2014, at 01:34 , Marko Tiikkaja <marko(at)joh(dot)to> wrote:
> It's me again, trying to find a solution to the most common mistakes I make. This time it's accidental shadowing of variables, especially input variables. I've wasted several hours banging my head against the wall while shouting "HOW CAN THIS VARIABLE ALWAYS BE NULL?". I can't believe I'm the only one. To give you a rough idea on how it works:
I like this, but think that the option should be just called plpgsql.warnings or plpgsql.warn_on and accept a list of warnings to enable. I'm sure you'll come up with more unsafe coding practices to warn about in the future - for example, consistent_into immediately comes to mind ;-)
best regards,
Florian Pflug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2014-01-15 06:11:06 | Re: Portal suddenly disappears? |
| Previous Message | Claudio Freire | 2014-01-15 06:00:37 | Re: Linux kernel impact on PostgreSQL performance |