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

Поиск
Список
Период
Сортировка
От ADRIANO BOLLER
Тема Re: RFC: Command Restrictions by INI file with Audit Logging (DROP/TRUNCATE/DELETE)
Дата
Msg-id 196a1398ae1.11a7442b7121908.5297274322243829962@wxsolucoes.com.br
обсуждение исходный текст
Ответ на Re: RFC: Command Restrictions by INI file with Audit Logging (DROP/TRUNCATE/DELETE)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Hi Guys

Please read suggestions:


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

Rua Rene Dinorah da Silveira, 70 - Tarumã - Curitiba - Paraná - Brasil
SKype/Telegram : adrianoboller




---- On seg, 05 mai 2025 12:01:10 -0400 tgl@sss.pgh.pa.us<tgl@sss.pgh.pa.us> wrote ----

"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

Вложения

В списке pgsql-hackers по дате отправления: