Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 052ACB5DC06 for ; Wed, 27 Jul 2011 17:29:02 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 87923-01-2 for ; Wed, 27 Jul 2011 20:28:55 +0000 (UTC) X-Greylist: delayed 00:06:24.660694 by SQLgrey-1.7.6 Received: from nm4.bullet.mail.ukl.yahoo.com (nm4.bullet.mail.ukl.yahoo.com [217.146.182.225]) by mail.postgresql.org (Postfix) with SMTP id 24B34B5DC0A for ; Wed, 27 Jul 2011 17:28:54 -0300 (ADT) Received: from [217.146.183.209] by nm4.bullet.mail.ukl.yahoo.com with NNFMP; 27 Jul 2011 20:22:29 -0000 Received: from [217.146.183.60] by tm2.bullet.mail.ukl.yahoo.com with NNFMP; 27 Jul 2011 20:22:29 -0000 Received: from [127.0.0.1] by omp1029.mail.ukl.yahoo.com with NNFMP; 27 Jul 2011 20:22:29 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 346343.88478.bm@omp1029.mail.ukl.yahoo.com Received: (qmail 15766 invoked by uid 60001); 27 Jul 2011 20:22:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1311798149; bh=VUe+m//gkgIaYMKFqF1dAezmSuxbc2fMC6kNqP0euTw=; 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=4fhGsRsgYGQLxvmdoB2xox7hNGjvzgVK5Ffu5bCpNzQJrVqgZy/YJmMlZ6pygpjjRT5112BhNkgfuj1ANE3LHnksZQn4ICMCFBfmmxizJ8wRUsoQFddk6/yTEFbFD04+7JpGJpuyinfXL3E+a1iTzoy+clNDBzvddIZ+Zggy6TE= 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=RxPnHT+vwn8RSjndnWBlFhhmxwgUhhTyjQznnJWxVbSueLded8TWAIdDTSxwkxepNE0/hC5yh09GDhNCHYHKIhjmr8yWKQu96xKFMmq6Y0eWPB2o8gHh/80xNZHsiZTRLmd8xpj0fLJDAI4WbTRe25NLe594D24HvrOal5WK5Ew=; X-YMail-OSG: sC8t8ocVM1l8kecmNUGSYc5JeG8FXywPQxwsFSdgcp43rkr 2Zd_3TAgcl2oHYt5drQpDVsBI_OrFrBnFb06X7O.SpkuJlaZvbmT_uFVM1Bo yJ9WamxzavjsWM65qRhod7tV.vRkHiEATZn2QKl6AZqK9MXzdBgzYQCrgdz7 sQIdGgYgJTk2Jy89IDlG9cPWuNIICPxqsR4C73.fX1FLS98qufhNYT_zaui. FkA..HwDx.v1D43bHhTfuZEvj_lB9cXaUo7z17U7Bw2XlJ57ckeya9uHnJ2W cTAifFrq6IQcrP6SkCylsyNafJ3KKD3xHFhD1c6akQaezsk6rVuf6_BwyOE7 kdWDe2yexyuXbkUwBvWRgoc4icWOBTdoKH6o17DFKpTy7lhHbhORSnuZ47tD H6Cx5uMA8jnQHcZHjphzw9SAAoqAq9eRjx6f_NexEiKgg8XbU9KMfQbdzt5I Oahvcip5bubUij9YL1IXzKpD0bsYW0MzkGg9guVQ- Received: from [86.26.177.166] by web26004.mail.ukl.yahoo.com via HTTP; Wed, 27 Jul 2011 21:22:29 BST X-Mailer: YahooMailWebService/0.8.112.310352 References: <1311784043.24356.YahooMailNeo@web26002.mail.ukl.yahoo.com> <10638.1311784321@sss.pgh.pa.us> <1311784785.5983.YahooMailNeo@web26004.mail.ukl.yahoo.com> <4E2FFB6E020000250003F81B@gw.wicourts.gov> Message-ID: <1311798149.1639.YahooMailNeo@web26004.mail.ukl.yahoo.com> Date: Wed, 27 Jul 2011 21:22:29 +0100 (BST) From: Glyn Astill Reply-To: Glyn Astill Subject: Re: Adding line to pg_hba.conf for a specific group makes superuser authentication fail in 9.0? To: Kevin Grittner , Tom Lane Cc: "pgsql-admin@postgresql.org" In-Reply-To: <4E2FFB6E020000250003F81B@gw.wicourts.gov> 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/197 X-Sequence-Number: 37976 > From: Kevin Grittner =0A=0A>Glyn Astill wrote:=0A> =0A>>=A0=A0How can I specifically catch sup= erusers?=0A> =0A> Create a group (nobody?) that you don't grant to any user= s.=A0 Only=0A> superusers will be a member of it.=0A> =0A=0AAh of course, s= imple, thanks Kevin.=0A=0AI can't help but feel that there should be someth= ing in the docs for 9.0 to specify this, since it is a behaviour difference= from 8.4 and earlier.=0A=0AThe docs (http://www.postgresql.org/docs/9.0/in= teractive/auth-pg-hba-conf.html) do say:=0A=0A"Recall that there is no real= distinction between users and groups=A0=A0=A0=A0=A0=A0=A0=A0in PostgreSQL;= a + mark really means "match any of the roles that are directly or indirec= tly members=A0=A0=A0=A0=A0=A0=A0=A0of this role", while a name without a + = mark matches=A0=A0=A0=A0=A0=A0=A0=A0only that specific role" =0A=0AMaybe th= e docs should be embellished to also say "since a superuser is automaticall= y considered a member of any group, it should be taken into account that na= mes with a + mark will affect all superusers (although this was not the cas= e prior to 9.0)" or something along those lines.=0A=0AGlyn=A0 =0A