pg.ddx.io pgaudit/pgaudit GitHub issues and pull requestshelp / color / mirror / Atom feed
[pgaudit/pgaudit] issue #288: Improvement - Put TRUNCATE in a separate audit class 5+ messages / 2 participants [nested] [flat]
* [pgaudit/pgaudit] issue #288: Improvement - Put TRUNCATE in a separate audit class @ 2025-08-28 15:47 "lessardjm (@lessardjm)" <noreply+lessardjm@github.com> 0 siblings, 0 replies; 5+ messages in thread From: lessardjm (@lessardjm) @ 2025-08-28 15:47 UTC (permalink / raw) To: pgaudit/pgaudit <noreply+pgaudit-pgaudit@github.com> When auditing by objects using pgaudit.role to limit the number of table audited, truncates are not audited. To audit truncates we need to audit writes on all tables (pgaudit.log=writes). Let say you have a logging table like an audit, history, etc., table that is always updated when a table is modified (insert/update/delete). For example - A table that logs changes performed by the application (application auditing) at the business objects level. - A hash table for inter - RDBMS platform replication that contains the hash of a business object (one hash by row of a parent table + child rows and grand-child rows). Configuring the audit for writes in all tables (pgaudit.log=writes) can easily double log file sizes or more. Configuring the audit for writes of only application tables (exclude secondary writes to audit, history, etc, tables) will not audit truncates. Most of the time, truncates are rare, but important to audit. Adding a new classes of audited statements (pgaudit.log=truncate) would be a nice feature in such cases. pgaudit.log=writes may still include truncates for backward compatibility. ^ permalink raw [nested|flat] 5+ messages in thread
* Re: [pgaudit/pgaudit] issue #288: Improvement - Put TRUNCATE in a separate audit class @ 2026-06-26 03:16 "dwsteele (@dwsteele)" <noreply+dwsteele@github.com> 3 siblings, 0 replies; 5+ messages in thread From: dwsteele (@dwsteele) @ 2026-06-26 03:16 UTC (permalink / raw) To: pgaudit/pgaudit <noreply+pgaudit-pgaudit@github.com> @dwsteele assigned @dwsteele. ^ permalink raw [nested|flat] 5+ messages in thread
* Re: [pgaudit/pgaudit] issue #288: Improvement - Put TRUNCATE in a separate audit class @ 2026-06-26 03:20 "dwsteele (@dwsteele)" <noreply+dwsteele@github.com> 3 siblings, 0 replies; 5+ messages in thread From: dwsteele (@dwsteele) @ 2026-06-26 03:20 UTC (permalink / raw) To: pgaudit/pgaudit <noreply+pgaudit-pgaudit@github.com> @dwsteele applied label "question". ^ permalink raw [nested|flat] 5+ messages in thread
* Re: [pgaudit/pgaudit] issue #288: Improvement - Put TRUNCATE in a separate audit class @ 2026-06-26 03:21 "dwsteele (@dwsteele)" <noreply+dwsteele@github.com> 3 siblings, 0 replies; 5+ messages in thread From: dwsteele (@dwsteele) @ 2026-06-26 03:21 UTC (permalink / raw) To: pgaudit/pgaudit <noreply+pgaudit-pgaudit@github.com> @dwsteele closed this. ^ permalink raw [nested|flat] 5+ messages in thread
* Re: [pgaudit/pgaudit] issue #288: Improvement - Put TRUNCATE in a separate audit class @ 2026-06-26 03:21 "dwsteele (@dwsteele)" <noreply+dwsteele@github.com> 3 siblings, 0 replies; 5+ messages in thread From: dwsteele (@dwsteele) @ 2026-06-26 03:21 UTC (permalink / raw) To: pgaudit/pgaudit <noreply+pgaudit-pgaudit@github.com> This seems reasonable but it is not something I'm planning to work on. You may submit a PR with the feature if you are interested. ^ permalink raw [nested|flat] 5+ messages in thread
end of thread, other threads:[~2026-06-26 03:21 UTC | newest] Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-08-28 15:47 [pgaudit/pgaudit] issue #288: Improvement - Put TRUNCATE in a separate audit class "lessardjm (@lessardjm)" <noreply+lessardjm@github.com> 2026-06-26 03:16 ` "dwsteele (@dwsteele)" <noreply+dwsteele@github.com> 2026-06-26 03:20 ` "dwsteele (@dwsteele)" <noreply+dwsteele@github.com> 2026-06-26 03:21 ` "dwsteele (@dwsteele)" <noreply+dwsteele@github.com> 2026-06-26 03:21 ` "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox