aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2006-11-22 04:17:03 +0000
committerBruce Momjian <bruce@momjian.us>2006-11-22 04:17:03 +0000
commitba2edcac4fd3c41b58a72f0244ebc0caaeead4af (patch)
tree6c49e76c88b2f63ef90d49eaedabbd1778eb2fed
parent8c556ce1c21c09a8d7f8e0a100cd00fd8faf437c (diff)
downloadpostgresql-ba2edcac4fd3c41b58a72f0244ebc0caaeead4af.tar.gz
postgresql-ba2edcac4fd3c41b58a72f0244ebc0caaeead4af.zip
Mention OIDs are now not created by default.
-rw-r--r--doc/FAQ12
-rw-r--r--doc/src/FAQ/FAQ.html16
2 files changed, 14 insertions, 14 deletions
diff --git a/doc/FAQ b/doc/FAQ
index 7036cfc6631..89292219a16 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Tue Nov 21 10:37:54 EST 2006
+ Last updated: Tue Nov 21 23:16:54 EST 2006
Current maintainer: Bruce Momjian (bruce@momjian.us)
@@ -728,11 +728,11 @@
4.12) What is an OID? What is a CTID?
- Every row that is created in PostgreSQL gets a unique OID unless
- created WITHOUT OIDS. OIDs are automatically assigned unique 4-byte
- integers that are unique across the entire installation. However, they
- overflow at 4 billion, and then the OIDs start being duplicated.
- PostgreSQL uses OIDs to link its internal system tables together.
+ If a table is created WITH OIDS, each row gets a unique a OID. OIDs
+ are automatically assigned unique 4-byte integers that are unique
+ across the entire installation. However, they overflow at 4 billion,
+ and then the OIDs start being duplicated. PostgreSQL uses OIDs to link
+ its internal system tables together.
To uniquely number rows in user tables, it is best to use SERIAL
rather than OIDs because SERIAL sequences are unique only within a
diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index 6231f266efb..146de2c240d 100644
--- a/doc/src/FAQ/FAQ.html
+++ b/doc/src/FAQ/FAQ.html
@@ -10,7 +10,7 @@
alink="#0000ff">
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
- <P>Last updated: Tue Nov 21 10:37:54 EST 2006</P>
+ <P>Last updated: Tue Nov 21 23:16:54 EST 2006</P>
<P>Current maintainer: Bruce Momjian (<A href=
"mailto:bruce@momjian.us">bruce@momjian.us</A>)
@@ -956,13 +956,13 @@ length</TD></TR>
<H3 id="item4.12">4.12) What is an <SMALL>OID</SMALL>? What is
a <SMALL>CTID</SMALL>?</H3>
- <P>Every row that is created in PostgreSQL gets a unique
- <SMALL>OID</SMALL> unless created <SMALL>WITHOUT OIDS</SMALL>.
- O<SMALL>ID</SMALL>s are automatically assigned unique 4-byte
- integers that are unique across the entire installation. However,
- they overflow at 4 billion, and then the O<SMALL>ID</SMALL>s start
- being duplicated. PostgreSQL uses <SMALL>OID</SMALL>s to link its
- internal system tables together.</P>
+ <P>If a table is created <SMALL>WITH OIDS</SMALL>, each row
+ gets a unique a <SMALL>OID</SMALL>. O<SMALL>ID</SMALL>s are
+ automatically assigned unique 4-byte integers that are unique
+ across the entire installation. However, they overflow at 4
+ billion, and then the O<SMALL>ID</SMALL>s start being duplicated.
+ PostgreSQL uses <SMALL>OID</SMALL>s to link its internal system
+ tables together.</P>
<P>To uniquely number rows in user tables, it is best to use
<SMALL>SERIAL</SMALL> rather than O<SMALL>ID</SMALL>s because