mirror of
https://github.com/postgres/postgres.git
synced 2025-06-27 23:21:58 +03:00
Update FAQ.
This commit is contained in:
2
doc/FAQ
2
doc/FAQ
@ -901,7 +901,7 @@ BYTEA bytea variable-length array of bytes
|
|||||||
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
|
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
|
one has reported this ever happening, and we plan to have the limit
|
||||||
removed before anyone does.
|
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
|
||||||
|
@ -1096,7 +1096,7 @@ 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
|
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
|
at 4 billion. No one has reported this ever happening, and we plan to
|
||||||
have the limit removed before anyone does.<P>
|
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
|
||||||
|
Reference in New Issue
Block a user