Tom Lane wrote:
> Koichi Suzuki <suzuki(dot)koichi(at)oss(dot)ntt(dot)co(dot)jp> writes:
>> Here's an idea and a patch for full page writes improvement.
> 
>> Idea:
>> (1) keep full page writes for ordinary WAL, make them available during
>> the crash recovery, -> recovery from inconsistent pages which can be
>> made at the crash,
>> (2) Remove them from the archive log except for those written during
>> online backup (between pg_start_backup and pg_stop_backup) -> small size
>> archive log.
> 
> Doesn't this break crash recovery on PITR slaves?

Compressed archive log contains the same data as full_page_writes off
case.   So the influence to PITR slaves is the same as full_page_writes off.

						K.Suzuki

> 
> 			regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
> 
>                http://www.postgresql.org/docs/faq
> 


-- 
Koichi Suzuki

In response to

• Re: Full page writes improvement at 2007-02-01 19:59:07 from Tom Lane

Responses

• Re: [HACKERS] Full page writes improvement at 2007-02-02 01:03:27 from Tom Lane

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2007-02-02 00:41:39
	Subject: Re: writing new regexp functions
Previous:	From: Gavin Sherry	Date: 2007-02-02 00:34:49
	Subject: Re: Bitmap index thoughts

pgsql-patches by date

Next:	From: Tom Lane	Date: 2007-02-02 00:41:39
	Subject: Re: writing new regexp functions
Previous:	From: Bruce Momjian	Date: 2007-02-02 00:29:46
	Subject: Re: [pgsql-patches] Fixed shared_preload_libraries on Win32