Re: Making pg_standby compression-friendly

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Koichi Suzuki" <koichi(dot)szk(at)gmail(dot)com>, "Charles Duffy" <Charles_Duffy(at)messageone(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Making pg_standby compression-friendly
Date: 2008-10-27 15:03:06
Message-ID: 490591DA.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>> "Koichi Suzuki" <koichi(dot)szk(at)gmail(dot)com> wrote:
> As Heikki pointed out, the issue is not to decompress the compressed
> WAL, but also how we can keep archive log still compressed after it
is
> handled by pg_standby.
>
> I'm afraid pg_standby cannot handle this solely, may need some
support
> by the pg core. For example, after closing archive log in archive
> recovery, pg_core can call some backend to re-compress the archive
log
> for later use.

Why decompress and re-compress? We're using simple bash scripts, so I
can't speak to pg_standby; but we just pipe the file through gunzip in
the script called by recovery.conf. The source file isn't modified --
it stays compressed for archiving.

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-10-27 15:05:24 Re: ERRORDATA_STACK_SIZE exceeded (server crash)
Previous Message Magnus Hagander 2008-10-27 14:37:33 Re: Parsing errors in pg_hba.conf