pgsql/ oc/src/sgml/user-manag.sgml oc/src/sgml ... - Mailing list pgsql-committers

From Marc G. Fournier
Subject pgsql/ oc/src/sgml/user-manag.sgml oc/src/sgml ...
Date
Msg-id 200109081524.f88FO0N46508@hub.org
Whole thread Raw
List pgsql-committers
CVSROOT:    /home/projects/pgsql/cvsroot
Module name:    pgsql
Changes by:    scrappy@hub.org    01/09/08 11:24:00

Modified files:
    doc/src/sgml   : user-manag.sgml
    doc/src/sgml/ref: initdb.sgml postgres-ref.sgml
    src/backend/catalog: genbki.sh
    src/backend/commands: user.c
    src/backend/utils/init: miscinit.c postinit.c
    src/backend/utils/misc: superuser.c
    src/bin/initdb : initdb.sh
    src/include    : miscadmin.h
    src/include/catalog: catversion.h pg_shadow.h

Log message:
    Make the world somewhat safe for (not from) DELETE FROM pg_shadow;

    Assign the fixed user id 1 to the user created by initdb.
    A stand-alone backend will always set the user id to 1.
    (Consequently, the name of that user is no longer important.)

    In stand-alone mode, the user id 1 will have implicit superuser
    status, to allow repairs even if there are no users defined.

    Print a warning message when starting in stand-alone mode when no
    users are defined.

    Disallow dropping the current user and session user.

    Granting/revoking superuser status also grants/revokes usecatupd.
    (Previously, it would never grant it back.  This could lead to "deadlocks".)

    CREATE USER and CREATE GROUP will start allocating user ids at 100
    (unless explicitly specified), to prevent accidental creation of a
    superuser (plus some room for future extensions).


pgsql-committers by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: pgsql/src/backend/utils/mb mbutils.c
Next
From: "Marc G. Fournier"
Date:
Subject: pgsql/src include/access/heapam.h backend/exec ...