Re: Values Logged in Logfile of postgres logs - Mailing list pgsql-admin

From Serkan Akdemir
Subject Re: Values Logged in Logfile of postgres logs
Date
Msg-id MW3PR19MB41855D56C51F0A4E93498A5DC3112@MW3PR19MB4185.namprd19.prod.outlook.com
Whole thread Raw
In response to Values Logged in Logfile of postgres logs  (Tejaswi K T <tejaswi.kt@gmail.com>)
List pgsql-admin
If you want to have some kind of auditing mechanism, you need to use pgaudit. 

Logging all statements to pglog is not a good idea. Even setting log_min_duration_statement = 0 is not a fesible too. You need to set this whenever you want to trace anything, later disable or set to reasonable value.

Tejaswi K T <tejaswi.kt@gmail.com> şunları yazdı (22 Nis 2024 23:01):


Hi Friends,

My postgres log has an insert statement with values too .

Is this safe of logging the values in the log file.
Is there a way to mask the values whenever DML operations happen. 

--------------------inserting record -------------------  
postgres=# insert into test (id) values(4);
INSERT 0 1

postgres=# show log_min_duration_statement;
 log_min_duration_statement
----------------------------
 0 -- to capture all statements happening 
(1 row)

2024-04-22 21:54:13.989 CEST [11805] postgres@postgres LOG:  duration: 10.455 ms  statement: insert into test (id) values(4);
2024-04-22 21:54:23.197 CEST [11805] postgres@postgres ERROR:  unrecognized configuration parameter "log_min_duration"

------------ the above log has values of what data got inserted as well. 

regards
Tejas

pgsql-admin by date:

Previous
From: Tejaswi K T
Date:
Subject: Values Logged in Logfile of postgres logs
Next
From: "Vitale, Anthony, Sony Music"
Date:
Subject: ERROR: index row size 2720 exceeds btree version 4 maximum 2704 for index in V14 but pg_column_size calculates 2701