Re: large inserts and fsync

From: Greg Smith <gsmith(at)gregsmith(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Aaron Burnett <aburnett(at)bzzagent(dot)com>, Sam Mason <sam(at)samason(dot)me(dot)uk>, pgsql-general(at)postgresql(dot)org
Subject: Re: large inserts and fsync
Date: 2008-09-06 08:45:58
Message-ID: Pine.GSO.4.64.0809052120290.21590@westnet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Aaron Burnett 2008-09-06 12:37:50 Re: large inserts and fsync
Previous Message Wouter Sergeyssels 2008-09-06 08:01:22 recover in single-user backend fails