Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
ba2edcac
Commit
ba2edcac
authored
Nov 22, 2006
by
Bruce Momjian
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Mention OIDs are now not created by default.
parent
8c556ce1
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
14 additions
and
14 deletions
+14
-14
doc/FAQ
doc/FAQ
+6
-6
doc/src/FAQ/FAQ.html
doc/src/FAQ/FAQ.html
+8
-8
No files found.
doc/FAQ
View file @
ba2edcac
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 unles
s
created WITHOUT OIDS. OIDs are automatically assigned unique 4-byt
e
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. OID
s
are automatically assigned unique 4-byte integers that are uniqu
e
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
...
...
doc/src/FAQ/FAQ.html
View file @
ba2edcac
...
...
@@ -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-byt
e
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 uniqu
e
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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment