RE: Detecting File Damage & Inconsistencies

From: "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>
To: 'Simon Riggs' <simon(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: RE: Detecting File Damage & Inconsistencies
Date: 2020-11-13 00:50:30
Message-ID: TYAPR01MB2990630F80BA6DD713DB6A5CFEE60@TYAPR01MB2990.jpnprd01.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
> If a rogue user/process is suspected, this would allow you to identify
> more easily the changes made by specific sessions/users.

Isn't that kind of auditing a job of pgAudit or log_statement = mod? Or, does "more easily" mean that you find pgAudit complex to use and/or log_statement's overhead is big?

Regards
Takayuki Tsunakawa

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2020-11-13 01:14:28 Use extended statistics to estimate (Var op Var) clauses
Previous Message Michael Paquier 2020-11-13 00:25:40 Re: remove spurious CREATE INDEX CONCURRENTLY wait