Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E72546505A2 for ; Sun, 13 Jul 2008 12:56:16 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 03540-02 for ; Sun, 13 Jul 2008 12:56:13 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from nabagan.bluegap.ch (nabagan.bluegap.ch [88.198.58.248]) by postgresql.org (Postfix) with ESMTP id 971B36505A1 for ; Sun, 13 Jul 2008 12:56:13 -0300 (ADT) Received: from [192.168.77.34] (p4FC1A33E.dip0.t-ipconnect.de [::ffff:79.193.163.62]) (AUTH: CRAM-MD5 markus@bluegap.ch, TLS: TLSv1/SSLv3, 256bits, AES256-SHA) by nabagan.bluegap.ch with esmtp; Sun, 13 Jul 2008 17:56:11 +0200 id 0135925B.487A259B.00001BB0 Message-ID: <487A259A.9090803@bluegap.ch> Date: Sun, 13 Jul 2008 17:56:10 +0200 From: Markus Wanner User-Agent: Mozilla-Thunderbird 2.0.0.14 (X11/20080509) MIME-Version: 1.0 To: Vincent Predoehl CC: pgsql-interfaces@postgresql.org Subject: Re: connecting with libpq interface References: <8EAB9EDC-BC0E-4C5F-BE0F-20F6DBAE1660@phoenixwebgroup.com> <19689.1215806725@sss.pgh.pa.us> <33C26302-6E84-440C-843D-F39A2F892CEE@phoenixwebgroup.com> In-Reply-To: <33C26302-6E84-440C-843D-F39A2F892CEE@phoenixwebgroup.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/12 X-Sequence-Number: 6770 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