Re: Archive log compression keeping physical log availablein the crash recovery - Mailing list pgsql-hackers

From Zeugswetter Andreas ADI SD
Subject Re: Archive log compression keeping physical log availablein the crash recovery
Date
Msg-id E1539E0ED7043848906A8FF995BDA57901C132F1@m0143.s-mxs.net
Whole thread Raw
In response to Re: Archive log compression keeping physical log available in the crash recovery  (Koichi Suzuki <suzuki.koichi@oss.ntt.co.jp>)
Responses Re: Archive log compression keeping physical log availablein the crash recovery  (Koichi Suzuki <suzuki.koichi@oss.ntt.co.jp>)
List 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


pgsql-hackers by date:

Previous
From: Jan Wieck
Date:
Subject: Re: Proposal: Commit timestamp
Next
From: Jan Wieck
Date:
Subject: Re: Proposal: Commit timestamp