Re: new to sql-ledger and postgresql.

[Olaf F. <ofa...@at...>]

Klav,

See the snippet below from the Postgres manual.  Perhaps sql-ledger is
trying to connect via TCP, but Postgres is only accepting connections via
UDP (the Postgres default, at least at one time).

-Olaf

=======================

3.3.2. Client Connection Problems
Although the error conditions possible on the client side are quite varied
and application-dependent, a few of them might be directly related to how
the server was started up. Conditions other than those shown below should be
documented with the respective client application.


psql: could not connect to server: Connection refused
        Is the server running on host server.joe.com and accepting
        TCP/IP connections on port 5432?
This is the generic "I couldn't find a server to talk to" failure. It looks
like the above when TCP/IP communication is attempted. A common mistake is
to forget the -i option to allow the postmaster to accept TCP/IP
connections.

Alternatively, you'll get this when attempting Unix-socket communication to
a local postmaster:

psql: could not connect to server: Connection refused
        Is the server running locally and accepting
        connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

----- Original Message -----
From: "klavs klavsen" <kl...@vs...>
To: "SQL-Ledger mailinglist" <sql...@li...>
Sent: Thursday, March 21, 2002 5:53 AM
Subject: new to sql-ledger and postgresql.