Re: [PATCH] add relation and block-level filtering to pg_waldump

From: Japin Li <japinli(at)hotmail(dot)com>
To: David Christensen <david(dot)christensen(at)crunchydata(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] add relation and block-level filtering to pg_waldump
Date: 2022-02-25 06:32:22
Message-ID: MEYP282MB1669791B8B59D6CF2C785BDAB63E9@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Fri, 25 Feb 2022 at 03:02, David Christensen <david(dot)christensen(at)crunchydata(dot)com> wrote:
> Greetings,
>
> This patch adds the ability to specify a RelFileNode and optional BlockNum to limit output of
> pg_waldump records to only those which match the given criteria. This should be more performant
> than `pg_waldump | grep` as well as more reliable given specific variations in output style
> depending on how the blocks are specified.
>
> This currently affects only the main fork, but we could presumably add the option to filter by fork
> as well, if that is considered useful.
>

Cool. I think we can report an error instead of reading wal files,
if the tablespace, database, or relation is invalid. Does there any
WAL record that has invalid tablespace, database, or relation OID?

--
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yugo NAGATA 2022-02-25 06:39:24 Re: Typo in pgbench messages.
Previous Message Kyotaro Horiguchi 2022-02-25 06:31:12 Re: Add checkpoint and redo LSN to LogCheckpointEnd log message