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 1D4C4D1B4E9 for ; Tue, 14 Oct 2003 22:19:25 +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 07569-01 for ; Tue, 14 Oct 2003 19:18:55 -0300 (ADT) Received: from mail.osdl.org (fw.osdl.org [65.172.181.6]) by svr1.postgresql.org (Postfix) with ESMTP id 8A38FD1B4ED for ; Tue, 14 Oct 2003 19:18:51 -0300 (ADT) Received: from osdl.org (markw@ibm-b.pdx.osdl.net [172.20.1.51]) by mail.osdl.org (8.11.6/8.11.6) with ESMTP id h9EMIWo27040; Tue, 14 Oct 2003 15:18:34 -0700 Message-Id: <200310142218.h9EMIWo27040@mail.osdl.org> Date: Tue, 14 Oct 2003 15:18:29 -0700 (PDT) From: markw@osdl.org Subject: Re: backup/restore - another area. To: threshar@torgo.978.org Cc: pgsql-performance@postgresql.org, linux-lvm@sistina.com In-Reply-To: <878ynu9ed5.fsf@stark.dyndns.tv> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/468 X-Sequence-Number: 4216 Jeff, I'm curious to what kind of testing you've done with LVM. I'm not currently trying any backup/restore stuff, but I'm running our DBT-2 workload using LVM. I've started collecting vmstat, iostat, and readprofile data, initially running disktest to gauge the performance. For anyone curious, I have some data on a 14-disk volume here: http://developer.osdl.org/markw/lvm/results.4/log/ and a 52-disk volume here: http://developer.osdl.org/markw/lvm/results.5/data/ Mark >Jeff writes: > > Idea #1: > Use an LVM and take a snapshop - archive that. > From the way I see it. the downside is the LVM will use a lot of space > until the snapshot is removed. Also PG may be in a slightly inconsistant > state - but this should "appear" to PG the same as if the power went out. > > For restore, simply unarchive this snapshot and point postgres at it. Let > it recover and you are good to go. > > Little overhead from what I see... > I'm leaning towards this method the more I think of it.