Re: proleakproof vs opr_sanity test - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: proleakproof vs opr_sanity test
Date
Msg-id CAB7nPqQRX9D2csaNmO4ZGPPh4UxKYgra0TeZMT5_65jn=sGRaA@mail.gmail.com
Whole thread Raw
In response to proleakproof vs opr_sanity test  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, May 29, 2015 at 12:09 AM, Tom Lane wrote:
> So I think we ought to fix xideqint4 to be marked leakproof and then
> add this test.  That would only be in HEAD though since it'd require
> an initdb.  Any objections?

FWIW, this makes sense.

> Is there a reason to believe that a
> built-in function might be leakproof when invoked from one function
> OID but not another?

I can't think about one after pondering about that a bit...
-- 
Michael



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: fsync-pgdata-on-recovery tries to write to more files than previously
Next
From: "Joshua D. Drake"
Date:
Subject: Re: RFC: Remove contrib entirely