Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nNJlC-0001Wu-0p for pgsql-hackers@arkaria.postgresql.org; Thu, 24 Feb 2022 19:26:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nNJlA-0004bm-5H for pgsql-hackers@arkaria.postgresql.org; Thu, 24 Feb 2022 19:26:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nNJl9-0004bd-NF for pgsql-hackers@lists.postgresql.org; Thu, 24 Feb 2022 19:26:39 +0000 Received: from mail-ej1-x630.google.com ([2a00:1450:4864:20::630]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nNJl6-0002r9-U1 for pgsql-hackers@postgresql.org; Thu, 24 Feb 2022 19:26:38 +0000 Received: by mail-ej1-x630.google.com with SMTP id gb39so6504766ejc.1 for ; Thu, 24 Feb 2022 11:26:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bowt-ie.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sWIMe7xqBfcXs7cRQyHYVTc708xRdiOjLRAGajuEheI=; b=lrFW1WOQ7MGV3Pb7Rkg4gePAjcEYavvKgmNF7dlGp91R0BqzeLnuLX8ua2Cq3s7aCZ 97kwfFouoltQl9Ws9SLfEb5V1xlgCQXjDGL9MeB4PkOeCcTh4kyrbJVwuI/0TUSf2raX 9hDD4WrkmBkx9Q7MkSkh0boNC3bnebqD9K98hkBEHxhqGKBii1Pl9hwUY8K5lAzbBIpu QilDoL+HqX7RUGh44HnI9LSkGCEhdv6GqoL/xoREJcajRFU4VFMC016JQGlR0iQpTdnJ qB+KpeyLOcOsuHaC51JlRr996fr+4QcRUvzj33cJEQH4j6fanuQN8JpWRwfu2DpV5lGu 6eRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sWIMe7xqBfcXs7cRQyHYVTc708xRdiOjLRAGajuEheI=; b=0IZKkk/Qj6/4cJ6CZWIxiWKXIMyb0X13w5Qnr1ysCOTFz2tqfhpz3iTru1Ot/pq0Q+ /vYioFUPW0hkv6kPNply4OQthCxyc9uTVxywTZ3ELWOmEjfrKFuQVg3ZvMf/bguNqUWG BbTdnMJzwb0UtHS1m5OhbP3k+rEwG27jSxBojuNuwkw6ibnrdLKuIziWSrifyEkSsFS0 R9j5L4lDZ8EL5nEb7LgQBCkEm1mPrlKHe6dJvEB/eKRSFoUTdH5QnHYiWlsdeWwQXjMn 33FNzaCEy6uO5O7CB1rK2XvWP3NRzALhCbZMqum+ROG+lV8cmY3ePhmF5W2kL76vEGaE rcow== X-Gm-Message-State: AOAM530Ju7odqCjHjKMjmq1CQ/I7LTq7rJjkt7e9DYl+JxnM7Y4Tns8g pBT+7yt9bVHiHfBq/88GlfQ1MFC5gLnVhXJrZhQGqA== X-Google-Smtp-Source: ABdhPJx7IL/uSfQ5XJGBza/xoH9e01PK+9GoWUQlNaqBq63dAGUTHL6601pgBtPt85wCUWC0oeCr9c+mk21CVCFxD/c= X-Received: by 2002:a17:906:1244:b0:6cf:118c:932f with SMTP id u4-20020a170906124400b006cf118c932fmr3425516eja.563.1645730795310; Thu, 24 Feb 2022 11:26:35 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Peter Geoghegan Date: Thu, 24 Feb 2022 11:26:09 -0800 Message-ID: Subject: Re: [PATCH] add relation and block-level filtering to pg_waldump To: David Christensen Cc: PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Feb 24, 2022 at 11:06 AM David Christensen wrote: > 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. Sounds useful to me. -- Peter Geoghegan