Re: pg_restore and transaction id wraparound
| От | Christopher Browne |
|---|---|
| Тема | Re: pg_restore and transaction id wraparound |
| Дата | |
| Msg-id | m38ym0tabz.fsf@wolfe.cbbrowne.com обсуждение исходный текст |
| Ответ на | pg_restore and transaction id wraparound (ow <oneway_111@yahoo.com>) |
| Ответы |
Re: pg_restore and transaction id wraparound
|
| Список | 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 по дате отправления: