Re: Fastest way to restore a database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scott Ribe <scott_ribe(at)killerbytes(dot)com>
Cc: Postgres General List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Fastest way to restore a database
Date: 2008-09-12 19:55:46
Message-ID: 15717.1221249346@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Scott Ribe <scott_ribe(at)killerbytes(dot)com> writes:
>> The worry expressed upthread about the transaction being "too large" is
>> unfounded, btw. Unlike some other DBs, PG doesn't have a finite-size
>> undo log.

> Sure, it won't fail. But would there be some point at which it would become
> slower than multiple transactions? Or is it always faster (or at least as
> fast)?

I can't think of any reason it would be slower.

There are certainly issues you could run into with very long
transactions, like vacuum not being able to remove bloat elsewhere.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Blazej 2008-09-12 20:37:09 Re: psql scripting tutorials
Previous Message Scott Ribe 2008-09-12 19:29:10 Re: Fastest way to restore a database