From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-hackers@postgresql.org, "Zeugswetter Andreas ADI SD" <ZeugswetterA@spardat.at>
Cc: Koichi Suzuki <suzuki.koichi@oss.ntt.co.jp>
Cc: pgsql-patches@postgresql.org
Subject: Re: [HACKERS] Full page writes improvement, code update
Date: Tue, 24 Apr 2007 14:19:30 -0400
Message-ID: <6589.1177438770@sss.pgh.pa.us> (raw)
In-Reply-To: <200704240831.42873.josh@agliodbs.com>
References: <460886E8.6040907@oss.ntt.co.jp>
<462D5A23.9060706@oss.ntt.co.jp>
<E1539E0ED7043848906A8FF995BDA57901F3FFCC@m0143.s-mxs.net>
<200704240831.42873.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
> Well, as a PG hacker I find the name wal_fullpage_optimization quite
> baffling and I think our general user base will find it even more so.
> Now that I have Koichi's explanation of the problem, I vote for simply
> slaving this to the PITR settings and not having a separate option at
> all.
The way to not have a separate option is to not need one, by having the
feature not cost anything extra in the first place. Andreas and I have
made the point repeatedly about how to do that.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, ZeugswetterA@spardat.at, suzuki.koichi@oss.ntt.co.jp, pgsql-patches@postgresql.org
Subject: Re: [HACKERS] Full page writes improvement, code update
In-Reply-To: <6589.1177438770@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox