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 1mYAZp-0005cg-Fl for pgsql-hackers@arkaria.postgresql.org; Wed, 06 Oct 2021 17:19:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mYAZo-0007Mr-E8 for pgsql-hackers@arkaria.postgresql.org; Wed, 06 Oct 2021 17:19:32 +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 1mYAZo-0007Mi-6T for pgsql-hackers@lists.postgresql.org; Wed, 06 Oct 2021 17:19:32 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mYAZm-0007lI-22 for pgsql-hackers@lists.postgresql.org; Wed, 06 Oct 2021 17:19:31 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1mYAZf-00007T-T8; Wed, 06 Oct 2021 13:19:23 -0400 Date: Wed, 6 Oct 2021 13:19:23 -0400 From: Bruce Momjian To: Jeremy Schneider Cc: Bharath Rupireddy , PostgreSQL Hackers , satyanarlapuram@gmail.com, marvin_liang@qq.com, actyzhang@outlook.com, Ashutosh Sharma Subject: Re: pg_walinspect - a new extension to get raw WAL data and WAL stats Message-ID: <20211006171923.GD20296@momjian.us> References: <20211005220707.GC24555@momjian.us> <47c04e88-7df8-963c-e32e-491260a09691@ardentperf.com> <20211006004310.GE24555@momjian.us> <9186c1cd-04b6-3dc9-40c5-5977dd854e36@ardentperf.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9186c1cd-04b6-3dc9-40c5-5977dd854e36@ardentperf.com> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Oct 6, 2021 at 09:56:34AM -0700, Jeremy Schneider wrote: > On 10/5/21 17:43, Bruce Momjian wrote: > > On Tue, Oct 5, 2021 at 03:30:07PM -0700, Jeremy Schneider wrote: > >> Specifically exposing pg_waldump functionality in SQL could speed up > >> finding bugs in the PG logical replication code. We found and fixed a > >> few over this past year, but there are more lurking out there. > > > > Uh, why is pg_waldump more important than other command line tool > > information? > > Going down the list of all other utilities in src/bin: > > * pg_amcheck, pg_config, pg_controldata: already available in SQL > * psql, pgbench, pg_dump: already available as client-side apps > * initdb, pg_archivecleanup, pg_basebackup, pg_checksums, pg_ctl, > pg_resetwal, pg_rewind, pg_upgrade, pg_verifybackup: can't think of any > possible use case outside server OS access, most of these are too low > level and don't even make sense in SQL > * pg_test_fsync, pg_test_timing: marginally interesting ideas in SQL, > don't feel any deep interest myself > > Speaking selfishly, there are a few reasons I would be specifically > interested in pg_waldump (the only remaining one on the list). This is the analysis I was looking for to understand if copying the features of command-line tools in extensions was a wise direction. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.