Vincent Predoehl wrote:
>>> terminate called after throwing an instance of 'pqxx::broken_connection'
>>> what(): could not connect to server: No such file or directory
>>> Is the server running locally and accepting
>>> connections on Unix domain socket "/var/run/
>> PQerrorMessage() should give you the same info in your standalone
>> libpq program.
> Yes it does:
> could not connect to server: No such file or directory
> Is the server running locally and accepting
> connections on Unix domain socket
Something similar has biten me before as well. I figured it is the
Debian packager's decision to put those socket files under
/var/run/postgresql/, which is not the Postgres standard.
In response to
pgsql-interfaces by date
|Next:||From: Sunil Khatri||Date: 2008-07-22 15:41:13|
|Subject: PQstatus is not returning|
|Previous:||From: Alvaro Herrera||Date: 2008-07-11 21:48:47|
|Subject: Re: connecting with libpq interface|