Skip site navigation (1) Skip section navigation (2)

Re: leakproof

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 (view raw or flat)
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. ;-)


In response to

Responses

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2012-02-26 16:06:54
Subject: Re: How to know a table has been modified?
Previous:From: Peter EisentrautDate: 2012-02-26 15:36:00
Subject: Re: Runtime SHAREDIR for testing CREATE EXTENSION

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group