Received: from dg.eisolution.com (dsl-209-81-146-10.dsl.iwc.net
	[209.81.146.10])
	by postgresql.org (8.11.3/8.11.4) with ESMTP id g0AIVfB74938
	for <pgsql-admin@postgresql.org>; Thu, 10 Jan 2002 13:31:46 -0500 (EST)
	(envelope-from marcm@eisolution.com)
Received: from marcmdelltop ([64.73.35.72])
	by dg.eisolution.com (8.11.6/8.11.2) with SMTP id g0AIXCf11275
	for <pgsql-admin@postgresql.org>; Thu, 10 Jan 2002 12:33:12 -0600
Message-ID: <010501c19a06$0e8d3120$620aa8c0@nmtransfer.com>
From: "Marc Mitchell" <marcm@eisolution.com>
To: <pgsql-admin@postgresql.org>
Subject: Grant all to Public & adding users
Date: Thu, 10 Jan 2002 12:38:49 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
X-Archive-Number: 200201/52
X-Sequence-Number: 2940

We have existing database where several tables have GRANT ALL TO PUBLIC.
However, when new users are added, they seem to get privilege problem until
another GRANT ALL TO PUBLIC is issued.  If this is truly the case (and
we're not crazy) then each time a new user is added, new GRANTs will have
to be executed.  Is this correct?  Is this intentional?  Anyone know a work
around?

MM