Search Postgresql Archives

Re: large inserts and fsync

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxx http://www.gregsmith.com Baltimore, MD


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux