Re: Compressing WAL

From: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Compressing WAL
Date: 2005-04-08 05:36:40
Message-ID: d355d3$2ht4$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance


""Jim C. Nasby"" <decibel(at)decibel(dot)org> writes
> Has anyone looked at compressing WAL's before writing to disk? On a
> system generating a lot of WAL it seems there might be some gains to be
> had WAL data could be compressed before going to disk, since today's
> machines are generally more I/O bound than CPU bound. And unlike the
> base tables, you generally don't need to read the WAL, so you don't
> really need to worry about not being able to quickly scan through the
> data without decompressing it.
> --

The problem is where you put the compression code? If you put it inside
XLogInsert lock or XLogWrite lock, which will hold the lock too long? Or
anywhere else?

Regards,
Qingqing

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2005-04-08 06:49:03 Re: prepared statements don't log arguments?
Previous Message Tom Lane 2005-04-08 05:03:16 Re: Weird psql crash

Browse pgsql-performance by date

  From Date Subject
Next Message Jeff Frost 2005-04-08 17:01:55 DATA directory on network attached storage
Previous Message Mischa Sandberg 2005-04-08 04:53:22 Re: multi-line copy (was: Re: COPY Hacks)