| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, ADRIANO BOLLER <adriano(at)wxsolucoes(dot)com(dot)br>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RFC: Command Restrictions by INI file with Audit Logging (DROP/TRUNCATE/DELETE) |
| Date: | 2025-05-06 09:53:39 |
| Message-ID: | 0FBC38C1-9235-440D-9E6E-24C0BF974C4F@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 5 May 2025, at 23:37, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org> wrote:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> 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.
The thread for adding --filter to pg_dump discussed file formats at length,
there might be learnings and arguments there which are of interest.
https://postgr.es/m/CAFj8pRB10wvW0CC9Xq=1XDs=zCQxer3cbLcNZa+qiX4cUH-G_A@mail.gmail.com
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yura Sokolov | 2025-05-06 09:57:29 | Re: bug: virtual generated column can be partition key |
| Previous Message | jian he | 2025-05-06 09:23:21 | Re: 2025-05-08 release announcement draft |