From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Vivek Khera <khera@kcilink.com>
Subject: Re: pg_restore taking 4 hours!
Date: Mon, 13 Dec 2004 10:43:28 -0800
Message-ID: <200412131043.28465.josh@agliodbs.com> (raw)
In-Reply-To: <83210A57-4D35-11D9-9C22-000A9578CFCC@kcilink.com>
References: <41ADA82A.7070405@carvalhaes.net>
<200412131025.54587.josh@agliodbs.com>
<83210A57-4D35-11D9-9C22-000A9578CFCC@kcilink.com>
Vivek,
> Do I need a correspondingly large checkpoint timeout then? Or does
> that matter much?
Yes, you do.
> And does this advice apply if the pg_xlog is on the same RAID partition
> (mine currently is not, but perhaps will be in the future)
Not as much, but it's still a good idea to serialize the load. With too few
segments, you get a pattern like:
Fill up segments
Write to database
Recycle segments
Fill up segments
Write to database
Recycle segments
etc.
Compared to doing it in one long run of a single cycle, considerble efficiency
is lost. With a proper 2-array setup, the segments become like a write
buffer for the database, and you want that buffer as large as you can afford
in order to prevent buffer cycling from interrupting database writes.
BTW, for members of the studio audience, checkpoint_segments of 256 is about
8GB.
--
Josh Berkus
Aglio Database Solutions
San Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, khera@kcilink.com
Subject: Re: pg_restore taking 4 hours!
In-Reply-To: <200412131043.28465.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox