Re: Archive log compression keeping physical log availablein the crash recovery

From: "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>
To: "Koichi Suzuki" <suzuki(dot)koichi(at)oss(dot)ntt(dot)co(dot)jp>, "Jim Nasby" <decibel(at)decibel(dot)org>
Cc: "PGSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Archive log compression keeping physical log availablein the crash recovery
Date: 2007-02-09 09:10:09
Message-ID: E1539E0ED7043848906A8FF995BDA57901C132F1@m0143.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Our evaluation result is as follows:
> Database size: 2GB
> WAL size (after 10hours pgbench run): 48.3GB
> gzipped size: 8.8GB
> removal of the physical log: 2.36GB
> fullpage_writes=off log size: 2.42GB

> I'm planning to do archive log size evalutation with other benchmarks
> such as DBT-2 as well.

Looks promising :-)

Did you use the standard 5 minute checkpoint_timeout?
Very nice would be a run with checkpoint_timeout increased
to 30 min, because that is what you would tune if you are concerned
about fullpage overhead.

Andreas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas ADI SD 2007-02-09 09:27:56 Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch
Previous Message Jeremy Drake 2007-02-09 09:08:57 Re: patch adding new regexp functions