From: | Christopher Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_restore and transaction id wraparound |
Date: | 2003-11-30 00:32:04 |
Message-ID: | m3isl2bssb.fsf@wolfe.cbbrowne.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
A long time ago, in a galaxy far, far away, oneway_111(at)yahoo(dot)com (ow) wrote:
> --- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Actually you can only have 4 billion SQL commands per xid, because the
>> CommandId datatype is also just 32 bits. I've never heard of anyone
>> running into that limit, though.
>
> Perhaps noone yet had a table with 4B records in pgSql. Otherwise,
> how would they dump/restore it?
I may have been guilty of hyperbole, by using the number 10 billion,
but not of proving this impossible.
If you had a table that large, dump/restore wouldn't have any XID
problems because the normal dump/restore involves copying the data out
(ONE query, ONE XID), and then reading it via the COPY command (again,
ONE query, ONE XID).
And I think I would be quite displeased if I had a table with that
many records, in any case, because dump/restore would take an
enormously long time as would reindexing.
--
(format nil "~S(at)~S" "cbbrowne" "ntlug.org")
http://cbbrowne.com/info/linuxdistributions.html
16-inch Rotary Debugger: A highly effective tool for locating problems
in computer software. Available for delivery in most major
metropolitan areas. Anchovies contribute to poor coding style.
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Elphick | 2003-11-30 22:29:35 | initdb should create a warning message [was Re: [ADMIN] Size on Disk] |
Previous Message | ow | 2003-11-29 20:11:47 | Re: pg_restore and transaction id wraparound |