Re: RFC: Command Restrictions by INI file with Audit Logging (DROP/TRUNCATE/DELETE)

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: ADRIANO BOLLER <adriano(at)wxsolucoes(dot)com(dot)br>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: RFC: Command Restrictions by INI file with Audit Logging (DROP/TRUNCATE/DELETE)
Date: 2025-05-05 15:26:36
Message-ID: CAKFQuwZSqs_R7727yHBRxrJXKGYgnJHaL22XboyGUaH03qJ9eQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sunday, May 4, 2025, ADRIANO BOLLER <adriano(at)wxsolucoes(dot)com(dot)br> wrote:

>
> Subject: RFC: INI-based Command Restriction Layer for DROP/TRUNCATE/DELETE
> with Audit Logging
>

I seem to recall similar features being discussed previously. Finding
those discussion would be nice.

>
> I’d be happy to prepare a full patch with unit tests and documentation for
> PostgreSQL 16+ if the concept is acceptable.
>
>
We are in feature freeze for PostgreSQL 18. It would be part of 19 at best.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2025-05-05 15:59:16 Re: PG 18 release notes draft committed
Previous Message David G. Johnston 2025-05-05 15:23:05 Re: fixing CREATEROLE