| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Don Baccus <dhogaza(at)pacifier(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: leakproof |
| Date: | 2012-02-26 15:39:09 |
| Message-ID: | 1330270749.32452.33.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On ons, 2012-02-22 at 10:56 -0500, Andrew Dunstan wrote:
> The trouble with "leakproof" is that it
> doesn't point to what it is that's not leaking, which is information
> rather than memory, as many might imagine (and I did) without further
> hints. I'm not sure any single English word would be as descriptive as
> I'd like.
Well, we have RETURNS NULL ON NULL INPUT, so maybe DOES NOT LEAK
INFORMATION. ;-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2012-02-26 16:06:54 | Re: How to know a table has been modified? |
| Previous Message | Peter Eisentraut | 2012-02-26 15:36:00 | Re: Runtime SHAREDIR for testing CREATE EXTENSION |