From: Qingqing Zhou <zhouqq@cs.toronto.edu>
To: pgsql-performance@postgresql.org
Subject: Re: Compressing WAL
Date: Fri, 8 Apr 2005 13:36:40 +0800
Message-ID: <d355d3$2ht4$1@news.hub.org> (raw)
References: <20050405040457.GK93835@decibel.org>
""Jim C. Nasby"" <decibel@decibel.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
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-performance@postgresql.org
Cc: zhouqq@cs.toronto.edu
Subject: Re: Compressing WAL
In-Reply-To: <d355d3$2ht4$1@news.hub.org>
* 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