pg_drop_events

pg_drop_events : logs transaction ids of drop table, drop column, drop materialized view statements

Overview

Packages

Source

pig build pkg pg_drop_events;		# build rpm/deb

Install

Make sure PGDG and PIGSTY repo available:

pig repo add pgsql -u   # add both repo and update cache

Install this extension with pig:

pig install pg_drop_events;		# install via package name, for the active PG version

pig install pg_drop_events -v 18;   # install for PG 18
pig install pg_drop_events -v 17;   # install for PG 17
pig install pg_drop_events -v 16;   # install for PG 16
pig install pg_drop_events -v 15;   # install for PG 15
pig install pg_drop_events -v 14;   # install for PG 14

Create this extension with:

CREATE EXTENSION pg_drop_events CASCADE; -- requires plpgsql

Usage

pg_drop_events: logs transaction ids of drop table, drop column, drop materialized view statements

The pg_drop_events extension uses event triggers to automatically log details about DROP operations on tables, columns, and materialized views. The logged information can be used for point-in-time recovery (PITR) after accidental drops.

Tracked Operations

• DROP TABLE
• DROP COLUMN (via ALTER TABLE)
• DROP MATERIALIZED VIEW

Logged Information

Example

CREATE EXTENSION pg_drop_events;

-- Drop a table
DROP TABLE t.t3;
-- NOTICE: table t.t3 dropped by transaction 1085.

-- Query the event log
SELECT * FROM pg_drop_events;

Point-in-Time Recovery

The logged data maps directly to PostgreSQL recovery parameters:

Use these values in postgresql.conf or recovery.conf to restore the database to a point just before the accidental drop.