Re: leakproof - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: leakproof
Date
Msg-id 1330270749.32452.33.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: leakproof  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: leakproof  ("A.M." <agentm@themactionfaction.com>)
List 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. ;-)



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Runtime SHAREDIR for testing CREATE EXTENSION
Next
From: "Kevin Grittner"
Date:
Subject: Re: How to know a table has been modified?