X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 193AED1B545 for ; Thu, 16 Oct 2003 17:04:13 +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 46275-01 for ; Thu, 16 Oct 2003 14:03:42 -0300 (ADT) Received: from dhcp-7-248.ma.lycos.com (waltham-nat.ma.lycos.com [209.202.205.1]) by svr1.postgresql.org (Postfix) with SMTP id 26009D1B532 for ; Thu, 16 Oct 2003 14:03:39 -0300 (ADT) Received: (qmail 30187 invoked from network); 16 Oct 2003 17:08:40 -0000 Received: from dhcp-7-41.ma.lycos.com (HELO squeegit) (10.124.7.41) by dhcp-7-248.ma.lycos.com with SMTP; 16 Oct 2003 17:08:40 -0000 Date: Thu, 16 Oct 2003 13:06:37 -0400 From: Jeff To: Josh Berkus Cc: markw@osdl.org, pgsql-performance@postgresql.org, linux-lvm@sistina.com, pgsql-admin@postgresql.org Subject: Re: [PERFORM] backup/restore - another area. Message-Id: <20031016130637.535f633f.threshar@torgo.978.org> In-Reply-To: <200310160949.59442.josh@agliodbs.com> References: <200310160949.59442.josh@agliodbs.com> X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/184 X-Sequence-Number: 10745 On Thu, 16 Oct 2003 09:49:59 -0700 Josh Berkus wrote: > Jeff, > > > The downside is > > this method will only work on that specific version of PG and it > > isn't the"cleanest" thing in the world since you are essentially > > simulating a power failure to PG. Luckly the WAL works like a champ. > > Also, these backups can be much larger since it has to include the > > indexes as well. but this is a price you have to pay. > > The other downside is, of course, that the database needs to be shut > down. > I left the DB up while doing this. Even had a program sitting around committing data to try and corrupt things. (Which is how I discovered I was doing the snapshot wrong) You could do pg_ctl stop; snapshot; pg_ctls tart for a "clean" image. -- Jeff Trout http://www.jefftrout.com/ http://www.stuarthamm.net/