On Fri, 17 Mar 2000, Kardos, Dr. Andreas wrote:
> Since I havn't got any reply from the hackers list, I'm resending this here
> to not lose it.
Sorry, I'm a little busy these days. Lots of mail to catch up with ...
> > On
> > CREATE USER username CREATEUSER
> > both pg_user.usesuper and pg_user
"Steve Nunez" <[EMAIL PROTECTED]> writes:
> www# ./configure --enable-locale --enable-multibyte --with-perl --with-odbc
> ...
> gmake[2]: *** No rule to make target `adt/SUBSYS.o', needed by `SUBSYS.o'.
> Stop.
> gmake[2]: Leaving directory `/local/src/postgresql-7.0beta2/src/backend/utils'
> gma
> I have spend a lot of time pondering exactly this issue when I wrote it. I
> guess you can flip it either way. On the one hand "CREATEUSER" has
> traditionally been synonymous with "superuser" (which is a problem, I
> believe), and catupd was created so that superusers are "protected from
> them
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
it seems in the beta2 release DBUSERID in pg_dumpall is the _name_ of the
user, so it doesn't need to be translated from the number to the name.
also ``create database ...'' does not take numbers for the encoding, so
the ENCODING variable does not ne
Applied. I should have realized I was using the username to look up the
username.
-- Start of PGP signed section.
> it seems in the beta2 release DBUSERID in pg_dumpall is the _name_ of the
> user, so it doesn't need to be translated from the number to the name.
>
> also ``create database ...''
