On Mon, Mar 25, 2013 at 07:07:42PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > We are taking this approach because PQconndefaults() doesn't have an API
> > to return the error cause, while other API calls do. Returning true so
> > we can later report the right error from a later API call just feels
> > wrong.
> Well, plan B would be to invent a replacement function that does have
> the ability to return an error message, but that seems like a lot of
> work for a problem that's so marginal that it wasn't noticed till now.
> (It's not so much creating the function that worries me, it's fixing
> clients to use it.)
> Plan C would be to redefine bogus value of PGSERVICE as not an error,
Given all of these poor options, is defining a PQconndefaults() as
perhaps out of memory or a service file problem really not better?
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
+ It's impossible for everything to be true. +
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2013-03-26 04:39:59|
|Subject: Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re:
Should array_length() Return NULL)|
|Previous:||From: Tom Lane||Date: 2013-03-26 03:14:25|
|Subject: Re: plpgsql_check_function - rebase for 9.3|