Horton

Re: pg_walinspect - a new extension to get raw WAL data and WAL stats

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: "Bossart, Nathan" <bossartn@amazon.com>
Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, "satyanarlapuram@gmail.com" <satyanarlapuram@gmail.com>, "marvin_liang@qq.com" <marvin_liang@qq.com>, "actyzhang@outlook.com" <actyzhang@outlook.com>, Ashutosh Sharma <ashu.coek88@gmail.com>
Date: 2021-09-10T01:51:21Z
Lists: pgsql-hackers 
On Thu, Sep 09, 2021 at 10:49:46PM +0000, Bossart, Nathan wrote:
> +1

A backend approach has the advantage that you can use the proper locks
to make sure that a segment is not recycled or removed by a concurrent
checkpoint, so that would be reliable.
--
Michael

Commits

  1. Doc build fix: remove tab from filelist.sgml.

  2. Add contrib/pg_walinspect.

  3. Simplify SRFs using materialize mode in contrib/ modules

  4. Invent "trusted" extensions, and remove the pg_pltemplate catalog.