On Friday 12 September 2008 15:55:46 Tom Lane wrote:
> Scott Ribe <[EMAIL PROTECTED]> 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
On Fri, 12 Sep 2008, Robert Treat wrote:
Don't forget to bump up checkpoint_timeout along with that... actually, I
blogged a couple of times on this topic
And with that there's enough information to start a dedicated page on this
topic: http://wiki.postgresql.org/wiki/Bulk_Loading_and_Restor
Scott Ribe <[EMAIL PROTECTED]> 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 multip
> 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
On Friday 12 September 2008 14:32:07 Greg Smith wrote:
> On Fri, 12 Sep 2008, William Garrison wrote:
> > Is there a definitive list of things to do?
>
> That section of the documention is pretty good:
> http://www.postgresql.org/docs/current/static/populate.html
>
> The main thing it's missing is
William Garrison <[EMAIL PROTECTED]> writes:
> So... if I am using pg_dump and pg_restore with a compressed backup,
> then it is using COPY, correct? And I think that would follow a CREATE
> TABLE statement as mentioned in the first link... so no WAL files written?
Only if you use --single-tran
Thanks so much!
So... if I am using pg_dump and pg_restore with a compressed backup,
then it is using COPY, correct? And I think that would follow a CREATE
TABLE statement as mentioned in the first link... so no WAL files written?
Greg Smith wrote:
On Fri, 12 Sep 2008, William Garrison wrot
On Fri, 12 Sep 2008, William Garrison wrote:
Is there a definitive list of things to do?
That section of the documention is pretty good:
http://www.postgresql.org/docs/current/static/populate.html
The main thing it's missing is a discussion of how to cut down on disk
commit overhead by eit
