X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id E8009D1B4D1 for ; Sat, 31 Jan 2004 05:08:18 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 12924-09 for ; Sat, 31 Jan 2004 01:08:16 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 8CC5BD1B43F for ; Sat, 31 Jan 2004 01:08:14 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i0V57r0V026691; Sat, 31 Jan 2004 00:07:53 -0500 (EST) To: Christopher Weimann Cc: "Joshua D. Drake" , Andrew Sullivan , pgsql-performance@postgresql.org Subject: Re: High Performance/High Reliability File system on SuSE64 In-reply-to: <20040124012247.GA40439@smtp.k12us.com> References: <001001c3e1d0$072b20e0$6601a8c0@thore> <401150F7.1040802@commandprompt.com> <20040123175544.GA12642@phlogiston.dyndns.org> <4011657B.2090501@commandprompt.com> <20040124012247.GA40439@smtp.k12us.com> Comments: In-reply-to Christopher Weimann message dated "Fri, 23 Jan 2004 20:22:47 -0500" Date: Sat, 31 Jan 2004 00:07:53 -0500 Message-ID: <26690.1075525673@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/344 X-Sequence-Number: 5518 Christopher Weimann writes: > You can do snapshots in FreeBSD 5.x with UFS2 as well but that ( > nor XFS snapshots ) will let you backup with the database server > running. Just because you will get the file exactly as it was at > a particular instant does not mean that the postmaster did not > still have some some data that was not flushed to disk yet. It *will* work, if you have an instantaneous filesystem snapshot covering the entire $PGDATA directory tree (both data files and WAL). Restarting the postmaster on the backup will result in a WAL replay sequence, and at the end the data files will be consistent. If this were not so, we'd not be crash-proof. The instantaneous snapshot is exactly equivalent to the on-disk state at the moment of a kernel crash or power failure, no? regards, tom lane