pg.ddx.io  pgaudit/pgaudit GitHub issues and pull requests  
help / color / mirror / Atom feed
From: dwsteele (@dwsteele) <noreply+dwsteele@github.com>
To: pgaudit/pgaudit <noreply+pgaudit-pgaudit@github.com>
Subject: Re: [pgaudit/pgaudit] PR #323: Do not log inserted or updated columns against the SELECT grant.
Date: Fri, 03 Jul 2026 02:58:09 +0000
Message-ID: <gh-pgaudit-pgaudit-323-rc3517197058@github.com> (raw)
In-Reply-To: <gh-pgaudit-pgaudit-323-rc3515598160@github.com>
References: <gh-pgaudit-pgaudit-323@github.com>
	<gh-pgaudit-pgaudit-323-rc3515598160@github.com>

(on sql/pgaudit.sql:342)

> Are non-matching columns here significant?

Yes. We are trying to show that *only* the returning clause generates an audit record. 

> i.e., would SET col2 = ... returning col2 behave the same way?

It would, since the part triggering the audit is the returning clause. I added a test in 46255392ffa to demonstrate this.

> Also do any OLD/NEW references matter here, or am I thinking of a trigger-only behavior?

They are not significant here since we are only examining the column ACLs. The actual values are not relevant. I added a test in 46255392ffa to prove this.

view thread (9+ messages)  latest in thread

Message-ID: <gh-pgaudit-pgaudit-323-rc3517197058@github.com>
Permalink:  ../gh-pgaudit-pgaudit-323-rc3517197058@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