From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Detecting File Damage & Inconsistencies |
Date: | 2020-11-12 07:52:59 |
Message-ID: | CANP8+jJHF0oATqMScxvB7P48S7Yfqzd3Z28syNzqYvxOBEiuJQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 12 Nov 2020 at 06:42, tsunakawa(dot)takay(at)fujitsu(dot)com
<tsunakawa(dot)takay(at)fujitsu(dot)com> wrote:
>
> From: Simon Riggs <simon(at)2ndquadrant(dot)com>
> > I would like to propose a few points that will help us detect file
> > damage, inconsistencies in files and track actions of users.
>
> Hello, Simon san. Long time no see. I'm happy to see you be back here recently.
Thank you, happy to be back. It's good to have the time to contribute again.
> What kind of improvement do you expect? What problems would this make detectable?
If a rogue user/process is suspected, this would allow you to identify
more easily the changes made by specific sessions/users.
> > * 2-byte pid (from MyProcPid)
>
> pid is 4 bytes on Windows. Isn't it also 4 byte on Linux when some kernel parameter is set to a certain value?
4 bytes is no problem, thanks for pointing that out.
--
Simon Riggs http://www.EnterpriseDB.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2020-11-12 08:04:43 | Re: ModifyTable overheads in generic plans |
Previous Message | Pavel Stehule | 2020-11-12 07:45:21 | Re: proposal: possibility to read dumped table's name from file |