Re: PQinitSSL broken in some use casesf - Mailing list pgsql-hackers

From Andrew Chernow
Subject Re: PQinitSSL broken in some use casesf
Date
Msg-id 4998C200.4060009@esilo.com
Whole thread Raw
In response to Re: PQinitSSL broken in some use casesf  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PQinitSSL broken in some use casesf  (Andrew Chernow <ac@esilo.com>)
List pgsql-hackers
> Maybe better, have it return a zero/nonzero error code; where one of the> possibilities for failure is "you passed a
bitI didn't understand".
 

Why not just return those bit(s) instead of an arbitrary code?  How about:

-1 = error (if it ever does anything that can fail) 0 = success (all bits known)>0 = unknown bits (remaining known bits
*have*been set)
 

-- 
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/


pgsql-hackers by date:

Previous
From: Zdenek Kotala
Date:
Subject: Re: casting in ORDER BY
Next
From: KaiGai Kohei
Date:
Subject: Re: SE-PostgreSQL and row level security