Re: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL - Mailing list pgsql-hackers

From Andreas Karlsson
Subject Re: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL
Date
Msg-id ffdee390-f977-4e75-ba86-36348ea6341d@proxel.se
Whole thread
In response to [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL  (surya poondla <suryapoondla4@gmail.com>)
Responses Re: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL
List pgsql-hackers
On 7/2/26 2:55 AM, surya poondla wrote:
> The patch adds contrib/pgtrashcan: a new extension that intercepts DROP 
> TABLE via a ProcessUtility hook and moves the relation to a
> reserved schema instead of destroying it, from where it can be restored 
> with pgtrashcan_restore or permanently deleted with
> pgtrashcan_purge. It is a fork of an existing pgtrashcan extension, 
> extended with additional features.
> 
> Any feedback is welcome.

Is there any reason your features cannot be added to the existing 
extension? Or that extension to be forked but still live outside core 
PostgresSQL?

-- 
Andreas Karlsson
Percona




pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Collect ALTER PUBLICATION commands for event triggers
Next
From: Haibo Yan
Date:
Subject: Re: Fix race in background worker termination for database