Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TNUam-0004SG-I6 for pgsql-admin@postgresql.org; Sun, 14 Oct 2012 20:15:20 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TNUah-0002B6-K0 for pgsql-admin@postgresql.org; Sun, 14 Oct 2012 20:15:19 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q9EKFDFl002604; Sun, 14 Oct 2012 16:15:13 -0400 (EDT) From: Tom Lane To: Jimy McDermott cc: pgsql-admin@postgresql.org Subject: Re: TCPIP connection on local host using md5 In-reply-to: References: Comments: In-reply-to Jimy McDermott message dated "Fri, 12 Oct 2012 14:48:32 -0700" Date: Sun, 14 Oct 2012 16:15:13 -0400 Message-ID: <2603.1350245713@sss.pgh.pa.us> X-Pg-Spam-Score: -2.3 (--) X-Archive-Number: 201210/44 X-Sequence-Number: 40160 Jimy McDermott writes: > pg_hba.conf: > # TYPE DATABASE USER ADDRESS METHOD > # "local" is for Unix domain socket connections only > local all all peer > # IPv4 local connections: > host all all 127.0.0.1/32 ident > # IPv6 local connections: > host all all ::1/128 ident > # Allow replication connections from localhost, by a user with the > # replication privilege. > host all all 192.168.20.250/32 md5 # > This line supports the remote connection that works great > host all report 127.0.0.1/32 md5 # > This line is intended to support the local connection that is failing pg_hba.conf lines are considered in order, so the second one (with the ident auth method) is matching the incoming connection before the last one ever gets considered. You need to re-order those lines. The rule of thumb is "most specific rule first". regards, tom lane