From: Markus Wanner <markus@bluegap.ch>
To: Vincent Predoehl <vpredoehl@phoenixwebgroup.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: connecting with libpq interface
Date: Sun, 13 Jul 2008 17:56:10 +0200
Message-ID: <487A259A.9090803@bluegap.ch> (raw)
In-Reply-To: <33C26302-6E84-440C-843D-F39A2F892CEE@phoenixwebgroup.com>
References: <8EAB9EDC-BC0E-4C5F-BE0F-20F6DBAE1660@phoenixwebgroup.com>
<19689.1215806725@sss.pgh.pa.us>
<33C26302-6E84-440C-843D-F39A2F892CEE@phoenixwebgroup.com>
Hi,
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/
>>> postgresql/.s.PGSQL.5432"?
>>
>> 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
> "/var/run/postgresql/.s.PGSQL.5432"?
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.
Regards
Markus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: markus@bluegap.ch, vpredoehl@phoenixwebgroup.com
Subject: Re: connecting with libpq interface
In-Reply-To: <487A259A.9090803@bluegap.ch>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox