rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

This is a small fix in FAQ. It just clean up some old comments and 

change an old -not-working piece of code.
This commit is contained in:
Bruce Momjian 2004-06-04 04:09:40 +00:00
parent bf2a115f2f
commit 768916d753
2 changed files with 12 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/FAQ
View File

@ -1,7 +1,7 @@
Frequently Asked Questions (FAQ) for PostgreSQL Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Mon Mar 29 00:07:11 EST 2004 Last updated: Fri Jun 4 00:09:16 EDT 2004
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
@ -965,11 +965,11 @@ BYTEA bytea variable-length byte array (null-byte safe)
all databases. If you want to change the OID to something else, or if all databases. If you want to change the OID to something else, or if
you want to make a copy of the table, with the original OIDs, there is you want to make a copy of the table, with the original OIDs, there is
no reason you can't do it: no reason you can't do it:
CREATE TABLE new_table(old_oid oid, mycol int); CREATE TABLE new_table(mycol int);
SELECT old_oid, mycol INTO new FROM old; SELECT oid AS old_oid, mycol INTO tmp_table FROM old_table;
COPY new TO '/tmp/pgtable'; COPY tmp_table TO '/tmp/pgtable';
DELETE FROM new; COPY new_table WITH OIDS FROM '/tmp/pgtable';
COPY new WITH OIDS FROM '/tmp/pgtable'; DROP TABLE tmp_table;
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 ever happening, and we plan to have the limit one has reported this ever happening, and we plan to have the limit

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

@ -10,7 +10,7 @@
alink="#0000ff"> alink="#0000ff">
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
<P>Last updated: Thu May 6 10:22:34 EDT 2004</P> <P>Last updated: Fri Jun 4 00:09:16 EDT 2004</P>
<P>Current maintainer: Bruce Momjian (<A href= <P>Current maintainer: Bruce Momjian (<A href=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR> "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
@ -1213,16 +1213,12 @@ BYTEA bytea variable-length byte array (null-byte safe)
of the table, with the original <SMALL>OID</SMALL>s, there is no of the table, with the original <SMALL>OID</SMALL>s, there is no
reason you can't do it:</P> reason you can't do it:</P>
<PRE> <PRE>
CREATE TABLE new_table(old_oid oid, mycol int); CREATE TABLE new_table(mycol int);
SELECT old_oid, mycol INTO new FROM old; SELECT oid AS old_oid, mycol INTO tmp_table FROM old_table;
COPY new TO '/tmp/pgtable'; COPY tmp_table TO '/tmp/pgtable';
DELETE FROM new; COPY new_table WITH OIDS FROM '/tmp/pgtable';
COPY new WITH OIDS FROM '/tmp/pgtable'; DROP TABLE tmp_table;
</PRE> </PRE>
<!--
CREATE TABLE new_table (mycol int);
INSERT INTO new_table (oid, mycol) SELECT oid, mycol FROM old_table;
-->
<P>O<SMALL>ID</SMALL>s are stored as 4-byte integers, and will <P>O<SMALL>ID</SMALL>s are stored as 4-byte integers, and will
overflow at 4 billion. No one has reported this ever happening, and overflow at 4 billion. No one has reported this ever happening, and
we plan to have the limit removed before anyone does.</P> we plan to have the limit removed before anyone does.</P>