From: pgguru (@pgguru) <noreply+pgguru@github.com>
To: pgaudit/pgaudit <noreply+pgaudit-pgaudit@github.com>
Subject: Re: [pgaudit/pgaudit] PR #325: Skip executor hooks when SELECT/DML auditing is not enabled.
Date: Mon, 20 Jul 2026 14:32:39 +0000
Message-ID: <gh-pgaudit-pgaudit-325-c5023425783@github.com> (raw)
In-Reply-To: <gh-pgaudit-pgaudit-325@github.com>
References: <gh-pgaudit-pgaudit-325@github.com>
What sort of regressions might this cause—someone relying on the previous behavior? (From what I can see, there shouldn't be any user-visible changes, so doesn't seem likely.). Some analysis indicates that the patch should map cleanly.
What is the official policy on back patches? If this fixes some of the hook ordering/stack errors seen when combining multiple extensions, then I could consider this a bug fix. However if it is only a performance improvement I'm not certain this would be considered a bugfix per se (i.e., it's not fixing a performance regression). That said, if the policy is more flexible in terms of the contract here, the patch itself seems fairly straightforward, so I'd be in favor of improving performance.
(I assume the reporting user would also appreciate the bump without having to wait for Pg 19).