Re: pg_restore and transaction id wraparound

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-28 22:08:48
Message-ID: m38ym0tabz.fsf@wolfe.cbbrowne.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Quoth oneway_111(at)yahoo(dot)com (ow):
> Hypothetical situation: a table containing, say, 10 billion rows is backed up
> and then restored with pg_restore. Would this lead to the transaction id
> wraparound issue since 10B rows are imported in one "batch"?

No.

Copying the 10 billion rows in only consumes one xid.

- If you're in "autocommit mode," then each SQL statement consumes one
xid.

- If you type in BEGIN;, then you could have 10 billion SQL
statements after that, and they would, altogether, consume 1 xid.
--
"aa454","@","freenet.carleton.ca"
http://www3.sympatico.ca/cbbrowne/sgml.html
To iterate is human; to recurse, divine.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Mark Carew 2003-11-28 22:11:36 Re: Problem with pg_dump / pg_restore
Previous Message Martijn van Oosterhout 2003-11-28 22:01:39 Re: [GENERAL] Misplaced modifier in Postgresql license