Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] Full page writes improvement, code update

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Richard Huxton" <dev(at)archonet(dot)com>,"Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>,"Koichi Suzuki" <suzuki(dot)koichi(at)oss(dot)ntt(dot)co(dot)jp>,<josh(at)agliodbs(dot)com>,<pgsql-hackers(at)postgresql(dot)org>,<pgsql-patches(at)postgresql(dot)org>
Subject: Re: [PATCHES] Full page writes improvement, code update
Date: 2007-03-30 21:24:29
Message-ID: 1175289869.4386.837.camel@silverbirch.site (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On Fri, 2007-03-30 at 16:35 -0400, Tom Lane wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> > Any page written during a backup has a backup block that would not be
> > removable by Koichi's tool, so yes, you'd still be safe.
> 
> How does it know not to do that?

Not sure what you mean, but I'll take a stab...

I originally questioned Koichi-san's request for a full_page_compress
parameter, which is how it would tell whether/not. After explanation, I
accepted the need for a parameter, but I think we're looking for a new
name for it.

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com



In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2007-03-30 21:34:45
Subject: Re: Minor changes to Recovery related code
Previous:From: Tom LaneDate: 2007-03-30 21:08:42
Subject: Re: Arrays of Complex Types

pgsql-patches by date

Next:From: Simon RiggsDate: 2007-03-30 21:34:45
Subject: Re: Minor changes to Recovery related code
Previous:From: Tom LaneDate: 2007-03-30 21:08:42
Subject: Re: Arrays of Complex Types

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group