aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/sequence.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2003-03-20 20:05:32 +0000
committerBruce Momjian <bruce@momjian.us>2003-03-20 20:05:32 +0000
commitb2e09fcd5ea47250136f8dcb8ff42092a9e8be07 (patch)
tree56649a3c3e63737f76acac98c60f64cc39c1d62d /src/backend/commands/sequence.c
parent0fe77d7283160fc9dc5b5cacd1a70502835350e3 (diff)
downloadpostgresql-b2e09fcd5ea47250136f8dcb8ff42092a9e8be07.tar.gz
postgresql-b2e09fcd5ea47250136f8dcb8ff42092a9e8be07.zip
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
Diffstat (limited to 'src/backend/commands/sequence.c')
0 files changed, 0 insertions, 0 deletions