From: | momjian(at)postgresql(dot)org (Bruce Momjian - CVS) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql-server/doc/src/sgml/ref alter_user.sgml |
Date: | 2003-03-20 20:05:32 |
Message-ID: | 20030320200532.751E6476352@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
CVSROOT: /cvsroot
Module name: pgsql-server
Changes by: momjian(at)postgresql(dot)org 03/03/20 15:05:32
Modified files:
doc/src/sgml/ref: alter_user.sgml
Log message:
This is not the only place in the system catalogs where NULL is
effectively used to mean a default value that could also be spelled
out explicitly. (ACLs behave that way, and useconfig/datconfig
do too IIRC.)
It's a bit of a hack, but it saves table space and backend code ---
without this convention the default would have to be inserted "manually"
since we have no mechanism to supply defaults when C code is forming a
new catalog tuple.
I'm inclined to leave the code alone. But Alvaro is right that it'd be
good to point out the 'infinity' option in the CREATE USER and ALTER
USER man pages. (Doc patch please?)
Alvaro Herrera
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian - CVS | 2003-03-20 21:00:49 | pgsql-server/src/test/regress/output misc.source |
Previous Message | Bruce Momjian - CVS | 2003-03-20 19:00:01 | pgsql-server/doc/src/sgml/ref select.sgml |