DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=nCJAld0UTKPRPCFJP5T7bTc1shtWX2ZqjmKHvjamIdByTP4zDdZZl4lCF+9anadJgjuv3IAMvmoOoi9pOohT0XyEkZ/DZkeNzF4DyUCR56kpUy1lfhJ5gTZH3Nb4z49oT+kvcReQIgJPS8W7HUT9dv/9ETUlQGKZohwxoBqsxxo=
Message-ID: <a778a7260703301737l486aa5ebo830f0ac269a1fb15@mail.gmail.com>
Date: Sat, 31 Mar 2007 09:37:01 +0900
From: "Koichi Suzuki" <koichi.szk@gmail.com>
To: pgsql-hackers@postgresql.org, pgsql-patches@postgresql.org
Subject: Re: [PATCHES] Full page writes improvement, code update
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Simon;
Tom;

Koichi is writing.

Your question is how to determine WAL record generated between
pg_start_backup and pg_stop_backup and here's an answer.

XLogInsert( ) already has a logic to determine if inserting WAL record
is between pg_start_backup and pg_stop_backup.   Currently it is used
to remove full_page_writes when full_page_writes=off.   We can use
this to mark WAL records.   We have one bit not used in WAL record
header, the last bit of xl_info, where upper four bits are used to
indicate the resource manager and three of the rest are used to
indicate number of full page writes included in the record.

So in my proposal, this unused bit is used to mark that full page
writes must not be removed at offline optimization by pg_complesslog.

Sorry I didn't have mailing list capability from home and have just
completed my subscription from
home.   I had to create new thread to continue my post.  Sorry for confusion.

Please refer to the original thread about this discussion.

Best Regards;

-- 
------
Koichi Suzuki