diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2001-09-08 15:24:00 +0000 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2001-09-08 15:24:00 +0000 |
| commit | c0d4d5473a09cb7f6682a84abaee29e087c5886c (patch) | |
| tree | b61a851605fb862d27c3764bc341de79a565bb6f /doc/src/sgml/ref/postgres-ref.sgml | |
| parent | fdbf796f3634ddf837a76f8146656299cd1d260f (diff) | |
| download | postgresql-c0d4d5473a09cb7f6682a84abaee29e087c5886c.tar.gz postgresql-c0d4d5473a09cb7f6682a84abaee29e087c5886c.zip | |
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).
Diffstat (limited to 'doc/src/sgml/ref/postgres-ref.sgml')
| -rw-r--r-- | doc/src/sgml/ref/postgres-ref.sgml | 23 |
1 files changed, 13 insertions, 10 deletions
diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml index fda88ae1d48..839a1e86a75 100644 --- a/doc/src/sgml/ref/postgres-ref.sgml +++ b/doc/src/sgml/ref/postgres-ref.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.18 2001/09/03 12:57:50 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.19 2001/09/08 15:24:00 petere Exp $ Postgres documentation --> @@ -35,7 +35,7 @@ Postgres documentation <arg>-i</arg> <arg>-L</arg> <arg>-N</arg> - <arg>-o <replaceable>file-name</replaceable></arg> + <arg>-o <replaceable>filename</replaceable></arg> <arg>-O</arg> <arg>-P</arg> <group> @@ -58,7 +58,7 @@ Postgres documentation <arg>-F</arg> <arg>-i</arg> <arg>-L</arg> - <arg>-o <replaceable>file-name</replaceable></arg> + <arg>-o <replaceable>filename</replaceable></arg> <arg>-O</arg> <arg>-p <replaceable>database</replaceable></arg> <arg>-P</arg> @@ -103,9 +103,12 @@ Postgres documentation </para> <para> - When running a stand-alone backend the session user name will - automatically be set to the current effective Unix user name. If - that user does not exist the server will not start. + When running a stand-alone backend, the session user will be set to + the user with id 1. This user does not actually have to exist, so + a stand-alone backend can be used to manually recover from certain + kinds of accidental damage to the system catalogs. Implicit + superuser powers are granted to the user with id 1 in stand-alone + mode. </para> <refsect2> @@ -157,14 +160,14 @@ Postgres documentation </varlistentry> <varlistentry> - <term>-o <replaceable class="parameter">file-name</replaceable></term> + <term>-o <replaceable class="parameter">filename</replaceable></term> <listitem> <para> Sends all debugging and error output to - <replaceable class="parameter">OutputFile</replaceable>. + <replaceable class="parameter">filename</replaceable>. If the backend is running under the <application>postmaster</application>, error messages are still sent to the frontend process as well as to - <replaceable class="parameter">OutputFile</replaceable>, + <replaceable class="parameter">filename</replaceable>, but debugging output is sent to the controlling tty of the <application>postmaster</application> (since only one file descriptor can be sent to an actual file). @@ -359,7 +362,7 @@ Postgres documentation </refsect1> <refsect1> - <title>See also</title> + <title>See Also</title> <para> <xref linkend="app-initdb">, |