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

Full page writes improvement

From: Koichi Suzuki <suzuki(dot)koichi(at)oss(dot)ntt(dot)co(dot)jp>
To: PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org>,pgsql-patches(at)postgresql(dot)org
Subject: Full page writes improvement
Date: 2007-02-01 02:07:27
Message-ID: 45C14B5F.4010406@oss.ntt.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
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.

Implementation:
(1) Mark WAL record whose full-page-writes can be removed,
(2) Remove full-page writes from the marked WAL record in archive
command, and
(3) Restore the removed full-page writes to make LSN consistent.

Included is a patch for this as well as archive and restore command source.

Patch is very small and I hope this to be included in 8.3.

-- 
Koichi Suzuki

Attachment: pg_lesslog.tar.gz
Description: application/gzip (34.9 KB)

Responses

pgsql-hackers by date

Next:From: Gavin SherryDate: 2007-02-01 02:24:41
Subject: Re: Data archiving/warehousing idea
Previous:From: Chris DunlopDate: 2007-02-01 02:01:34
Subject: Data archiving/warehousing idea

pgsql-patches by date

Next:From: Bruce MomjianDate: 2007-02-01 02:38:36
Subject: Re: DROP FUNCTION failure: cache lookup failed for relation X
Previous:From: Mark KirkwoodDate: 2007-02-01 01:17:24
Subject: Re: [pgsql-patches] Patch to avoid gprof profiling overwrites

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