Re: large inserts and fsync

Yeah, the backup is standard operating procedure before the start of the release process.

I'm going to try a few of the suggestions offered here first, then fall back on the fsync option if I can't get an appreciable increase in speed.

thanks all for the help and thoughts.

-----Original Message-----
From: Greg Smith [mailto:gsmith(at)gregsmith(dot)com]
Sent: Sat 9/6/2008 4:45 AM
To: Tom Lane
Cc: Aaron Burnett; Sam Mason; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] large inserts and fsync

On Fri, 5 Sep 2008, Tom Lane wrote:

> The trouble with turning fsync off is that a system crash midway through
> the import might leave you with a corrupt database. If you're willing
> to start over from initdb then okay, but if you are importing into a
> database that already contains valuable data, I wouldn't recommend it.

If you have enough disk space, realistically if you're running with fsync
off you should setup enough PITR features to get a base backup first, or
just copy the database directory if you can take the server down a bit.
Then your worst case becomes just starting over from that backup rather
than initdb.

--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD