Horton

Re: leakproof

Peter Eisentraut <peter_e@gmx.net>

View thread
From: Peter Eisentraut <peter_e@gmx.net>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, Jeff Janes <jeff.janes@gmail.com>, Don Baccus <dhogaza@pacifier.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-02-26T15:39:09Z
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. ;-)