database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-08 22:02:03 +03:00
Code

Update FAQ.

Browse Source
This commit is contained in:
Bruce Momjian 2000-07-27 19:22:20 +00:00
parent 1c753e1ffb
commit 1ee0d4a992
2 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/FAQ
View File

@ -900,6 +900,10 @@ BYTEA bytea variable-length array of bytes
DELETE FROM new; DELETE FROM new;
COPY new WITH OIDS FROM '/tmp/pgtable'; COPY new WITH OIDS FROM '/tmp/pgtable';
OIDs are stored as 4-byte integers, and will overflow at 4 billion. No
one has reported this every happening, and we plan to have the limit
removed before anyone does.
TIDs are used to identify specific physical rows with block and offset TIDs are used to identify specific physical rows with block and offset
values. Tids change after rows are modified or reloaded. They are used values. Tids change after rows are modified or reloaded. They are used
by index entries to point to physical rows. by index entries to point to physical rows.

4
doc/src/FAQ/FAQ.html
View File

@ -1095,6 +1095,10 @@ no reason you can't do it:
--> -->
</PRE><P> </PRE><P>
O<small>ID</small>s are stored as 4-byte integers, and will overflow
at 4 billion. No one has reported this every happening, and we plan to
have the limit removed before anyone does.<P>
T<small>ID</small>s are used to identify specific physical rows with block and offset T<small>ID</small>s are used to identify specific physical rows with block and offset
values. Tids change after rows are modified or reloaded. They are used values. Tids change after rows are modified or reloaded. They are used
by index entries to point to physical rows.<P> by index entries to point to physical rows.<P>