Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e6UMYlB06140 for ; Sun, 30 Jul 2000 18:34:47 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id SAA07631; Sun, 30 Jul 2000 18:34:45 -0400 (EDT) To: "David Lloyd-Jones" cc: pgsql-interfaces@postgresql.org Subject: Re: PSQL Working, but PGAccess Not Connecting. In-reply-to: <000701bffa74$88159790$406c7bd8@WORKGROUP> References: <200007301621.SAA02908@beertje.william.bogus> <000601bffa64$a38bb960$46647bd8@WORKGROUP> <1655.964993215@sss.pgh.pa.us> <000701bffa74$88159790$406c7bd8@WORKGROUP> Comments: In-reply-to "David Lloyd-Jones" message dated "Sun, 30 Jul 2000 18:21:27 -0400" Date: Sun, 30 Jul 2000 18:34:45 -0400 Message-ID: <7628.964996485@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200007/206 "David Lloyd-Jones" writes: > than one can read them) but I don't see how this adds up: I'm not on a > network, and PSQL, which is a front end to PostgreSQL, just like PGAccess is > supposed to be, is running fine. By default, psql connects via a Unix-socket path, not by TCP. PGAccess is written differently and always tries to connect by TCP. If you try to start psql with "-h localhost" or some such, it will try TCP and fail in the same way ... regards, tom lane