| From: | Markus Wanner <markus(at)bluegap(dot)ch> |
|---|---|
| To: | Vincent Predoehl <vpredoehl(at)phoenixwebgroup(dot)com> |
| Cc: | pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: connecting with libpq interface |
| Date: | 2008-07-13 15:56:10 |
| Message-ID: | 487A259A.9090803@bluegap.ch |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sunil Khatri | 2008-07-22 15:41:13 | PQstatus is not returning |
| Previous Message | Alvaro Herrera | 2008-07-11 21:48:47 | Re: connecting with libpq interface |