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 2555A8B9B31 for ; Tue, 22 Feb 2005 16:14:36 +0000 (GMT) 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 15443-10 for ; Tue, 22 Feb 2005 16:14:27 +0000 (GMT) Received: from 9.hellooperator.net (cpc3-cdif2-3-0-cust202.cdif.cable.ntl.com [81.103.32.202]) by svr1.postgresql.org (Postfix) with ESMTP id 126718B9E6E for ; Tue, 22 Feb 2005 16:14:25 +0000 (GMT) Received: from [10.4.0.5] (helo=eris.tenfour) by 9.hellooperator.net with esmtp (Exim 4.43) id 1D3cg3-0000Fi-Rs for pgsql-admin@postgresql.org; Tue, 22 Feb 2005 16:14:24 +0000 Received: from rasputnik by eris.tenfour with local (Exim 4.44 (FreeBSD)) id 1D3cg3-0009kI-Iy for pgsql-admin@postgresql.org; Tue, 22 Feb 2005 16:14:23 +0000 Date: Tue, 22 Feb 2005 16:14:23 +0000 From: Dick Davies To: PostgreSQL Admin Subject: Re: pg_hba.conf Message-ID: <20050222161423.GX66519@eris.tenfour> Reply-To: Dick Davies References: <20050222115641.GR66519@eris.tenfour> <20050222144751.GD22550@wolff.to> <9543.1109085518@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9543.1109085518@sss.pgh.pa.us> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.491 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL X-Spam-Level: * X-Archive-Number: 200502/223 X-Sequence-Number: 16391 * Tom Lane [0218 15:18]: > Perhaps easier would be to set "PGSSLMODE=allow" (or even "disable") in > the client environment. This will work for libpq-based clients; there > may be something equivalent if you are using other software. Thanks Tom, I'll give that a go. > Also: why aren't you just using a Unix socket? We never do SSL over > Unix sockets. As I said, it's set to 'trust' and restricted to a local group. Also, the deletion/rebuilding of the socket causes the application to lose the db connection, hopefully it will be more forgiving of a server bounce over IP. -- 'Oh, wait you're serious. Let me laugh even harder.' -- Bender Rasputin :: Jack of All Trades - Master of Nuns