Re: [HACKERS] Full page writes improvement

From: Koichi Suzuki <suzuki(dot)koichi(at)oss(dot)ntt(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] Full page writes improvement
Date: 2007-02-02 00:39:38
Message-ID: 45C2884A.50607@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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

Responses

Browse pgsql-hackers by date

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

Browse pgsql-patches by date

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