From: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, ADRIANO BOLLER <adriano(at)wxsolucoes(dot)com(dot)br>, "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 21:37:51 |
Message-ID: | 87wmauwxg0.fsf@wibble.ilmari.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> 2. The choice of .INI format for the config file seems a bit
> non-simpatico for Postgres. We have nothing else that uses that,
The pg_service.conf format is pretty .INI-like, it even calls itself
that in the docs:
Either service file uses an “INI file” format where the section name
is the service name and the parameters are connection parameters;
- https://www.postgresql.org/docs/current/libpq-pgservice.html
> 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.
JSON isn't very human-friendly for writing, it's more of a data
interchange format that happens to be human-readable.
> regards, tom lane
- ilmari
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-05-05 22:45:24 | Re: disabled SSL log_like tests |
Previous Message | Bruce Momjian | 2025-05-05 20:15:36 | Re: PG 18 release notes draft committed |