From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Message-Id: <20031016130637.535f633f.threshar@torgo.978.org> In-Reply-To: <200310160949.59442.josh@agliodbs.com> References: <200310160949.59442.josh@agliodbs.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [linux-lvm] Re: [PERFORM] backup/restore - another area. Sender: linux-lvm-admin@sistina.com Errors-To: linux-lvm-admin@sistina.com Reply-To: linux-lvm@sistina.com List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: Date: Thu Oct 16 14:06:03 2003 List-Id: Content-Type: text/plain; charset="us-ascii" To: Josh Berkus Cc: markw@osdl.org, pgsql-performance@postgresql.org, linux-lvm@sistina.com, pgsql-admin@postgresql.org 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/