X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 01921528A9 for ; Thu, 16 Jun 2005 20:00:20 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 64850-07 for ; Thu, 16 Jun 2005 23:00:17 +0000 (GMT) Received: from smtp.duo-county.com (smtp.duo-county.com [66.38.0.221]) by svr1.postgresql.org (Postfix) with ESMTP id B5455528B2 for ; Thu, 16 Jun 2005 20:00:15 -0300 (ADT) Received: from localhost.localdomain (15-066.mod.duo-county.com [66.38.15.66]) by bn9.blue.net (8.12.10/8.12.10/SMTP) with ESMTP id j5GN0Dij012992; Thu, 16 Jun 2005 18:00:13 -0500 (CDT) Received: from dlb by localhost.localdomain with local (Exim 4.50) id 1Dj0t8-0000ZF-Ju; Thu, 16 Jun 2005 15:22:58 -0500 Date: Thu, 16 Jun 2005 15:22:58 -0500 To: Tom Lane Cc: pgsql-admin@postgresql.org Subject: Re: Connecting via localhost pg-8.0.3 Message-ID: <20050616202258.GA1557@localhost.localdomain> Mail-Followup-To: Tom Lane , pgsql-admin@postgresql.org References: <20050615022603.GA1615@localhost.localdomain> <27553.1118805754@sss.pgh.pa.us> <20050616020048.GA1912@localhost.localdomain> <10056.1118894915@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10056.1118894915@sss.pgh.pa.us> User-Agent: Mutt/1.5.9i From: David X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.111 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200506/121 X-Sequence-Number: 17876 On Thu, Jun 16, 2005 at 12:08:35AM -0400, Tom Lane wrote: > David writes: > > Well, you guessed correctly. It was a configuration problem. By > > inserting the line: > > unix_socket_directory = '/var/run/postgresql' > > into postgresql.conf, it works as expected. > > Well, you've still got an issue here somewhere, because if your server > and client libraries came from the same build then they ought to agree > on this without any help from the config file. AFAIK, Debian hasn't > changed their policy about where to put the socket, so it seems like you > must be using a server that didn't come from Debian. dlb@localhost:~$ apt-cache policy postgresql-8.0 postgresql-8.0: Installed: 8.0.3-5 Candidate: 8.0.3-5 Version Table: *** 8.0.3-5 0 90 ftp://ftp.us.debian.org sid/main Packages 100 /var/lib/dpkg/status There is a bug report at bugs.debian.org/postgresql-8.0 (also in the new postgresql-common package) relating to the location of the socket. I'd seen this report before posting my original message, but things didn't click until I read your reply. Anyway, there was a suggestion by someone that unix_socket_directory needed to be specified. I do not know now where where the Debian 7.4 socket was located, as I had no need to look into that.