X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 14774D1B8D5 for ; Mon, 25 Aug 2003 12:13:55 -0300 (ADT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 44727-04 for ; Mon, 25 Aug 2003 12:13:23 -0300 (ADT) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id 7F2F1D1B8AA for ; Mon, 25 Aug 2003 12:13:22 -0300 (ADT) Received: (qmail 17793 invoked by uid 500); 25 Aug 2003 15:19:14 -0000 Date: Mon, 25 Aug 2003 10:19:14 -0500 From: Bruno Wolff III To: Chris M Cc: pgsql-admin@postgresql.org Subject: Re: template1 database... Message-ID: <20030825151914.GA17781@wolff.to> Mail-Followup-To: Chris M , pgsql-admin@postgresql.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/286 X-Sequence-Number: 10007 On Sun, Aug 24, 2003 at 00:38:35 +0800, Chris M wrote: > > The link is very good. But another question. > In PostgreSQL, a superuser can modify almost everything in the > databases. But I don't think that should be the default. Maybe > adding an option is better. When a superuser want to change > something owned by the system, he or she can turn the option > on, then do what he want. After that, the option should be turned > back to off. This is usually accomplished by logging in as a normal user for most tasks and only using a superuser account when it is needed.