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

From Dagfinn Ilmari Mannsåker
Subject Re: RFC: Command Restrictions by INI file with Audit Logging (DROP/TRUNCATE/DELETE)
Date
Msg-id 87wmauwxg0.fsf@wibble.ilmari.org
Whole thread Raw
In response to Re: RFC: Command Restrictions by INI file with Audit Logging (DROP/TRUNCATE/DELETE)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.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



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: PG 18 release notes draft committed
Next
From: Tom Lane
Date:
Subject: Re: disabled SSL log_like tests