| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | surya poondla <suryapoondla4(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL |
| Date: | 2026-07-24 20:39:54 |
| Message-ID: | ffdee390-f977-4e75-ba86-36348ea6341d@proxel.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haibo Yan | 2026-07-24 20:48:26 | Re: Fix race in background worker termination for database |
| Previous Message | Jacob Brazeal | 2026-07-24 20:04:34 | bug: query returns different result with and without memoization. |