pg.ddx.io  pgaudit/pgaudit GitHub issues and pull requests  
help / color / mirror / Atom feed
[pgaudit/pgaudit] issue #280: Update PGAudit docs to document its consistency model
7+ messages / 2 participants
[nested] [flat]

* [pgaudit/pgaudit] issue #280: Update PGAudit docs to document its consistency model
@ 2025-07-22 19:36  "baumand-amazon (@baumand-amazon)" <noreply+baumand-amazon@github.com>
  0 siblings, 0 replies; 7+ messages in thread

From: baumand-amazon (@baumand-amazon) @ 2025-07-22 19:36 UTC (permalink / raw)
  To: pgaudit/pgaudit <noreply+pgaudit-pgaudit@github.com>

It is my understanding that PGAudit logs are not transactional in the way that statements in a DB transaction are. In other words, when a transaction is committed in the DB there's a window where the host can power off or crash and lose the associated PGAudit entry.
EG: A crash after the WAL is flushed but before the PGAudit log disk write is made persistent (ie - PGAudit doesn't fsync). Another example could be a transaction committing and then PGAudit encountering a disk full error on the log partition.

A comparative example from MySql which I believe has the same consistency model - https://dev.mysql.com/doc/refman/8.4/en/audit-log-logging-configuration.html
"Regardless of strategy, logging occurs on a best-effort basis, with no guarantee of consistency."

PGAudit positions itself as an audit and compliance tool - https://github.com/pgaudit/pgaudit/blob/main/README.md
Therefore being clear and explicit about guarantees for logging is important for users.

It's my understanding that PGAudit uses `ereport`. And `ereport` does not (of course, for perf and availability reasons) perform an `fsync` after every write nor does it propagate errors if there's an issue completing the write.

^ permalink  raw  [nested|flat] 7+ messages in thread

* Re: [pgaudit/pgaudit] issue #280: Update PGAudit docs to document its consistency model
@ 2025-07-22 20:25  "baumand-amazon (@baumand-amazon)" <noreply+baumand-amazon@github.com>
  5 siblings, 0 replies; 7+ messages in thread

From: baumand-amazon (@baumand-amazon) @ 2025-07-22 20:25 UTC (permalink / raw)
  To: pgaudit/pgaudit <noreply+pgaudit-pgaudit@github.com>

@baumand-amazon closed this.

^ permalink  raw  [nested|flat] 7+ messages in thread

* Re: [pgaudit/pgaudit] issue #280: Update PGAudit docs to document its consistency model
@ 2025-07-31 16:36  "baumand-amazon (@baumand-amazon)" <noreply+baumand-amazon@github.com>
  5 siblings, 0 replies; 7+ messages in thread

From: baumand-amazon (@baumand-amazon) @ 2025-07-31 16:36 UTC (permalink / raw)
  To: pgaudit/pgaudit <noreply+pgaudit-pgaudit@github.com>

@baumand-amazon reopened this.

^ permalink  raw  [nested|flat] 7+ messages in thread

* Re: [pgaudit/pgaudit] issue #280: Update PGAudit docs to document its consistency model
@ 2026-06-26 02:42  "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
  5 siblings, 0 replies; 7+ messages in thread

From: dwsteele (@dwsteele) @ 2026-06-26 02:42 UTC (permalink / raw)
  To: pgaudit/pgaudit <noreply+pgaudit-pgaudit@github.com>

@dwsteele assigned @dwsteele.

^ permalink  raw  [nested|flat] 7+ messages in thread

* Re: [pgaudit/pgaudit] issue #280: Update PGAudit docs to document its consistency model
@ 2026-06-26 02:42  "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
  5 siblings, 0 replies; 7+ messages in thread

From: dwsteele (@dwsteele) @ 2026-06-26 02:42 UTC (permalink / raw)
  To: pgaudit/pgaudit <noreply+pgaudit-pgaudit@github.com>

@dwsteele applied label "enhancement".

^ permalink  raw  [nested|flat] 7+ messages in thread

* Re: [pgaudit/pgaudit] issue #280: Update PGAudit docs to document its consistency model
@ 2026-06-26 02:56  "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
  5 siblings, 0 replies; 7+ messages in thread

From: dwsteele (@dwsteele) @ 2026-06-26 02:56 UTC (permalink / raw)
  To: pgaudit/pgaudit <noreply+pgaudit-pgaudit@github.com>

@dwsteele closed this.

^ permalink  raw  [nested|flat] 7+ messages in thread

* Re: [pgaudit/pgaudit] issue #280: Update PGAudit docs to document its consistency model
@ 2026-06-26 02:56  "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
  5 siblings, 0 replies; 7+ messages in thread

From: dwsteele (@dwsteele) @ 2026-06-26 02:56 UTC (permalink / raw)
  To: pgaudit/pgaudit <noreply+pgaudit-pgaudit@github.com>

This makes sense, thank you. I have added a disclaimer to our caveats (0d4ac66d17f1).

^ permalink  raw  [nested|flat] 7+ messages in thread


end of thread, other threads:[~2026-06-26 02:56 UTC | newest]

Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-07-22 19:36 [pgaudit/pgaudit] issue #280: Update PGAudit docs to document its consistency model "baumand-amazon (@baumand-amazon)" <noreply+baumand-amazon@github.com>
2025-07-22 20:25 ` "baumand-amazon (@baumand-amazon)" <noreply+baumand-amazon@github.com>
2025-07-31 16:36 ` "baumand-amazon (@baumand-amazon)" <noreply+baumand-amazon@github.com>
2026-06-26 02:42 ` "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
2026-06-26 02:42 ` "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
2026-06-26 02:56 ` "dwsteele (@dwsteele)" <noreply+dwsteele@github.com>
2026-06-26 02:56 ` "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