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

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

From: Richard Huxton <dev(at)archonet(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: 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 11:48:47
Message-ID: 460CF91F.8040904@archonet.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Simon Riggs wrote:
> On Fri, 2007-03-30 at 11:27 +0100, Richard Huxton wrote:
> 
>> Is that always true? Could the backup not pick up a partially-written 
>> page? Assuming it's being written to as the backup is in progress. (We 
>> are talking about when disk blocks are smaller than PG blocks here, so 
>> can't guarantee an atomic write for a PG block?)
> 
> 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.
> 
> i.e. between pg_start_backup() and pg_stop_backup() we always use full
> page writes, even if you are running in full_page_writes=off mode.

Ah, that's OK then.

-- 
   Richard Huxton
   Archonet Ltd

In response to

pgsql-hackers by date

Next:From: Hannu KrosingDate: 2007-03-30 12:14:17
Subject: Re: Proposal: include PL/Proxy into core
Previous:From: NikhilSDate: 2007-03-30 11:26:30
Subject: Re: UPDATE using sub selects

pgsql-patches by date

Next:From: Peter EisentrautDate: 2007-03-30 12:23:27
Subject: Re: COPY-able sql log outputs
Previous:From: Heikki LinnakangasDate: 2007-03-30 11:28:32
Subject: Re: Make CLUSTER MVCC-safe

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