Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id BC91D1C7037E for ; Tue, 13 Dec 2011 21:39:32 -0400 (AST) Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Radod-0007Uj-Q3 for pgsql-docs@postgresql.org; Wed, 14 Dec 2011 01:39:32 +0000 Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id pBE1dEo03975; Tue, 13 Dec 2011 20:39:14 -0500 (EST) From: Bruce Momjian Message-Id: <201112140139.pBE1dEo03975@momjian.us> Subject: Re: CREATE USER In-Reply-To: To: Scott Marlowe Date: Tue, 13 Dec 2011 20:39:14 -0500 (EST) CC: Tom Lane , Jaime Casanova , pgsql-docs X-Mailer: ELM [version 2.4ME+ PL124 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Pg-Spam-Score: -4.2 (----) X-Archive-Number: 201112/37 X-Sequence-Number: 7144 Scott Marlowe wrote: > On Tue, Dec 13, 2011 at 4:36 PM, Bruce Momjian wrote: > > Tom Lane wrote: > >> Jaime Casanova writes: > >> > I just notice that when you create a user using CREATE USER and give > >> > the user the ability to create other users it gets created as > >> > SUPERUSER. > >> > >> Are you talking about the CREATEUSER option? ?That is documented, quite > >> clearly I think: > >> > >> ? ? ? CREATEUSER > >> ? ? ? NOCREATEUSER > >> > >> ? ? ? These clauses are an obsolete, but still accepted, spelling of > >> ? ? ? SUPERUSER and NOSUPERUSER. Note that they are not equivalent to > >> ? ? ? CREATEROLE as one might naively expect! > >> > >> The only way we could really make this any better is to remove these > >> keywords, which might be something to consider. ?The preferred SUPERUSER > >> spelling has been accepted since 8.1 ... is that long enough to ensure > >> everyone's converted their client-side tools? ?Probably not :-( > > > > How does this relate to people restoring pre-8.1 pg_dumpall dumps? > > Seems removing this option would cause the restore to fail. > > True, but 1: that's a really old release, and you should always dump > from the version you're going to not, going from, and 2: If you dumped > with 8.1 from 8.1 you're likely to have plenty of other issues loading > into later versions as well. How about it's marked as deprecated to > be removed in the next major release (9.1) and removed the one after > that (9.2)? Well, I know we support the new pg_dump dumping back to 7.1, but I don't know what our policy is for accepting old dumps. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +