Re: RFC: Command Restrictions by INI file with Audit Logging (DROP/TRUNCATE/DELETE) - Mailing list pgsql-hackers

Hi Guys

Please read suggestions:

https://grok.com/share/bGVnYWN5_365c76f0-3086-4231-9e5d-8dd99c9f3d2b

Suggestion with json

Please 

Best Regards

ADRIANO BOLLER CEO WX SOLUÇÕES LTDA  CNPJ: 14.421.060/0001-92 Desenvolvimento de Sistemas e Consultoria WX Representante Windev, Webdev, Windev Mobile HOSPEDAGEM WEBDEV É COM O SERVERWX Tel. :   ++55 41 99949 1800  /  +55 41 99851 9291 Rua Rene Dinorah da Silveira, 70 - Tarumã - Curitiba - Paraná - Brasil SKype/Telegram : adrianoboller Mail : adriano@wxsolucoes.com.br ou adrianoboller@gmail.com  Site :  http://wxsolucoes.com.br

"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Sunday, May 4, 2025, ADRIANO BOLLER <adriano@wxsolucoes.com.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 don't have an opinion on whether this is actually a feature we want,
but a couple of thoughts:

1. This seems to overlap a whole lot with one intended use-case for
event triggers. You could likely build it as an extension, relying
on an event trigger to get control at the right places.

2. The choice of .INI format for the config file seems a bit
non-simpatico for Postgres. We have nothing else that uses that,
which for starters means you'd have to write your own parser.
Something that might integrate better is JSON; we already have
code for that, and use-cases such as backup manifest files.

            regards, tom lane