Re: pg_restore and transaction id wraparound - Mailing list pgsql-admin

From Christopher Browne
Subject Re: pg_restore and transaction id wraparound
Date
Msg-id m38ym0tabz.fsf@wolfe.cbbrowne.com
Whole thread Raw
In response to pg_restore and transaction id wraparound  (ow <oneway_111@yahoo.com>)
Responses Re: pg_restore and transaction id wraparound  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
Quoth oneway_111@yahoo.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.

pgsql-admin by date:

Previous
From: Richard Welty
Date:
Subject: Re: [GENERAL] Misplaced modifier in Postgresql license
Next
From: Bruce Momjian
Date:
Subject: Re: Misplaced modifier in Postgresql license