From: Josh Berkus <josh@agliodbs.com>
To: Zeugswetter Andreas ADI SD <ZeugswetterA@spardat.at>
Cc: pgsql-hackers@postgresql.org, "Koichi Suzuki" <suzuki.koichi@oss.ntt.co.jp>
Cc: pgsql-patches@postgresql.org
Subject: Re: [HACKERS] Full page writes improvement, code update
Date: Wed, 25 Apr 2007 11:27:13 -0700
Message-ID: <200704251127.13624.josh@agliodbs.com> (raw)
In-Reply-To: <E1539E0ED7043848906A8FF995BDA57901F40143@m0143.s-mxs.net>
References: <460886E8.6040907@oss.ntt.co.jp>
<200704240831.42873.josh@agliodbs.com>
<E1539E0ED7043848906A8FF995BDA57901F40143@m0143.s-mxs.net>
Andreas,
> Writing to a different area was considered in pg, but there were more
> negative issues than positive.
> So imho pg_compresslog is the correct path forward. The current
> discussion is only about whether we want a more complex pg_compresslog
> and no change to current WAL, or an increased WAL size for a less
> complex implementation.
> Both would be able to compress the WAL to the same "archive log" size.
Huh? As conceived, pg_compresslog does nothing to lower log volume for
general purposes, just on-disk storage size for archiving. It doesn't help
us at all with the tremendous amount of log we put out for an OLTP server,
for example.
Not that pg_compresslog isn't useful on its own for improving warm standby
managability, but it's completely separate from addressing the "we're logging
too much" issue.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
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: 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: <200704251127.13624.josh@agliodbs.com>
* 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