Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id 21386B5DC04
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed, 27 Jul 2011 13:39:59 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 49808-04-5
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed, 27 Jul 2011 16:39:53 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from nm18.bullet.mail.ukl.yahoo.com (nm18.bullet.mail.ukl.yahoo.com
	[217.146.183.192])
	by mail.postgresql.org (Postfix) with SMTP id C7FE6B5DC14
	for <pgsql-admin@postgresql.org>; Wed, 27 Jul 2011 13:39:51 -0300 (ADT)
Received: from [217.146.183.217] by nm18.bullet.mail.ukl.yahoo.com with NNFMP;
	27 Jul 2011 16:39:50 -0000
Received: from [217.146.183.173] by tm10.bullet.mail.ukl.yahoo.com with NNFMP;
	27 Jul 2011 16:39:50 -0000
Received: from [127.0.0.1] by omp1014.mail.ukl.yahoo.com with NNFMP;
	27 Jul 2011 16:39:50 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 864738.54757.bm@omp1014.mail.ukl.yahoo.com
Received: (qmail 11051 invoked by uid 60001); 27 Jul 2011 16:39:50 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024;
	t=1311784790; bh=rzKKMt5s7prbFyX6fo1VmrJN4kCDtbSdamJIwGiuTjI=;
	h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=guVk3heAiKRTvMHfzizUQ7hugwjI0CztGOzyQuYyHvZvvYWyjqHWQdOdoGRfSR6ZB2nECvg37NXMExB/mH8W+jQce0Z1zXgDPhw+GLQUV3pNRe6N4S5qQ0DKqbY1w5m7WgwiOxxE7B2yg7hGxjOGY3kDCLfPVdyGsvvCHgws6yw=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk;
	h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=JinvbcK1QyIxkcxnLpfR6VmzxjqYl/YAACewaurEdzZU2ml9QMgtVVy/ZHbpf9uOzve7wNJjTJm5zOIZCSSZ1FkituZQnVAteoOCYdVYpqum1ZdFZia+TcpTSjTWt9KydQJXS7qtePVmPnKCulEkBiTyQNN2oo03j6PDMq92UmA=;
X-YMail-OSG: BzrzFc0VM1kEWKxI_SQly3Khj2sDiJMFQc3OfxTifzajk2v
	opfKEwRa19R2f4VLSvS8FTKYHSbuvtGEuIGPhhWU.DaRP36MOVOXe0GYfjUi
	Uk9l1HqSEzDgNPtAQemHGfBML7X7Al4gkiXJRfmIjIXvyjpmYbENHwJzRc5s
	CFykIALTB1TWY.7P45PK1oY1yv3iYABwNIhB8w7Z6DzgCLdgYs9ZhoUlRmBo
	VYk5siD_uis7PNed7P24kSoN0aKLptV37_N9r9qjGla_3XmEVR0HBqqsWneE
	.pfpbjh54UhCAqTwy6RxGRUvZzNUM4axOktrstQKwgloY9e9UlW5y_vIJEgQ
	4It5CrzxqGbP_Blgl.nGNtjB_EtQAsYO7D6Tf4O8_QiFDzHnRRLKCUKJ6nVC
	8wDZqUndeLiEVGJuJKLOOng--
Received: from [83.100.146.195] by web26004.mail.ukl.yahoo.com via HTTP;
	Wed, 27 Jul 2011 17:39:45 BST
X-Mailer: YahooMailWebService/0.8.112.310352
References: <1311784043.24356.YahooMailNeo@web26002.mail.ukl.yahoo.com>
	<10638.1311784321@sss.pgh.pa.us>
Message-ID: <1311784785.5983.YahooMailNeo@web26004.mail.ukl.yahoo.com>
Date: Wed, 27 Jul 2011 17:39:45 +0100 (BST)
From: Glyn Astill <glynastill@yahoo.co.uk>
Reply-To: Glyn Astill <glynastill@yahoo.co.uk>
Subject: Re: Adding line to pg_hba.conf for a specific group makes superuser
	authentication fail in 9.0?
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
In-Reply-To: <10638.1311784321@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.899 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001
X-Spam-Level: 
X-Archive-Number: 201107/194
X-Sequence-Number: 37973

> From: Tom Lane <tgl@sss.pgh.pa.us>=0A=0A>G lyn Astill <glynastill@yahoo.c=
o.uk> writes:=0A>>  I'm having what's hopefully a fairly trivial issue here=
 with =0A> pg_hba.conf in 9.0.4; when I add in the following line=0A> =0A>>=
  =A0=A0=A0=A0=A0=A0=A0 host=A0 =A0 all=A0 =A0 =A0 =A0  +ad_users=A0  10.10=
.0.0/16=A0 =A0 =A0 =A0 =A0 ldap <ldap =0A> details>=0A> =0A>>  If I try to =
log in with a superuser account from the 10.10.0.0/16 network =0A> it appea=
rs to try to authenticate it against that entry via ldap.=0A> =0A>>  This d=
idn't happen in 8.4.8, what could I be missing?=0A> =0A> Well, a superuser =
is automatically considered a member of any group,=0A> so a match to that l=
ine would be expected IMO.=A0 If you don't want that,=0A> you need some mor=
e-specific line ahead of it to catch superusers.=0A> =0A> =A0=A0=A0 =A0=A0=
=A0 =A0=A0=A0 regards, tom lane=0A>=0A=0AWell that's all new to me, surely =
this is a bug?=0A=0AHow can I specifically catch superusers?=0A