Postgres Pro
Downloads
Home   >   mailing lists

RE: Detecting File Damage & Inconsistencies - Mailing list pgsql-hackers

From tsunakawa.takay@fujitsu.com
Subject RE: Detecting File Damage & Inconsistencies
Date
Msg-id TYAPR01MB2990630F80BA6DD713DB6A5CFEE60@TYAPR01MB2990.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: Detecting File Damage & Inconsistencies  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Detecting File Damage & Inconsistencies  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Tree view 
From: Simon Riggs <simon@2ndquadrant.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
complexto use and/or log_statement's overhead is big?
 


Regards
Takayuki Tsunakawa

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: remove spurious CREATE INDEX CONCURRENTLY wait
Next
From: Tomas Vondra
Date:
Subject: Use extended statistics to estimate (Var op Var) clauses