Re: large inserts and fsync - Mailing list pgsql-general

From Greg Smith
Subject Re: large inserts and fsync
Date
Msg-id Pine.GSO.4.64.0809052120290.21590@westnet.com
Whole thread Raw
In response to Re: large inserts and fsync  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
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@gregsmith.com http://www.gregsmith.com Baltimore, MD

pgsql-general by date:

Previous
From: "Wouter Sergeyssels"
Date:
Subject: recover in single-user backend fails
Next
From: "Aaron Burnett"
Date:
Subject: Re: large inserts and fsync