Re: libpq thread locking during SSL connection start

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: libpq thread locking during SSL connection start
Date: 2013-08-01 17:42:25
Message-ID: 20130801174225.GP2706@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Alvaro Herrera (alvherre(at)2ndquadrant(dot)com) wrote:
> pgsecure_open_client() returns -1 if it can't lock the mutex. This is a
> problem because the callers are not prepared for that return value. I
> think it should return PGRES_POLLING_FAILED instead, after setting an
> appropriate error message in conn->errorMessage.

Ah, right, adding it there was a bit of a late addition, tbh.

> initialize_SSL() fails to set an error message. The return code of -1
> seems fine here.

Right, will improve.

Thanks!

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2013-08-01 17:48:13 Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Previous Message Alvaro Herrera 2013-08-01 17:34:33 Re: libpq thread locking during SSL connection start