Re: pg_stat_wal: tracking the compression effect

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: katouknl(at)oss(dot)nttdata(dot)com
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pg_stat_wal: tracking the compression effect
Date: 2022-08-26 02:55:27
Message-ID: 20220826.115527.709213176821152954.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Thu, 25 Aug 2022 16:04:50 +0900, Ken Kato <katouknl(at)oss(dot)nttdata(dot)com> wrote in
> Accumulating the values, which indicates how much space is saved by
> each compression (size before compression - size after compression),
> and keep track of how many times compression has happened. So that one
> can know how much space is saved on average.

Honestly, I don't think its useful much.
How about adding them to pg_waldump and pg_walinspect instead?

# It further widens the output of pg_waldump, though..

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2022-08-26 03:09:32 Re: pg_stat_wal: tracking the compression effect
Previous Message Amit Kapila 2022-08-26 02:11:00 Re: [PATCH] Fix alter subscription concurrency errors