public inbox for [email protected]  

help / color / mirror / Atom feed

From: Colin 't Hart <[email protected]>
To: Greg Sabino Mullane <[email protected]>
Cc: PostgreSQL General <[email protected]>
Subject: Re: Using pgAudit to audit interesting tables for all users except for batch user?
Date: Tue, 18 Nov 2025 16:55:06 +0100
Message-ID: <CAMon-aSyCvDk924RuP=BU5B4qsFAwJidWzQKmSEMgfL5KXKodQ@mail.gmail.com> (raw)
In-Reply-To: <CAKAnmmLRzMWc8qsKzu7uYoCVTm2fvME3+DqeeXcT6v1JCjiRPw@mail.gmail.com>
References: <CAMon-aRf-XS+wVEnVvP58GtojYENywx+s9pUjwz5omADdLP1NA@mail.gmail.com>
	<CAKAnmmLRzMWc8qsKzu7uYoCVTm2fvME3+DqeeXcT6v1JCjiRPw@mail.gmail.com>

Duh, I feel silly now :-)

Works perfectly.

Many thanks,

Colin

On Tue, 18 Nov 2025 at 16:11, Greg Sabino Mullane <[email protected]>
wrote:

> On Tue, Nov 18, 2025 at 4:18 AM Colin 't Hart <[email protected]>
> wrote:
>
>> alter user <batchuser> set pgaudit.log to 'none';
>>
>
> That's close! pgaudit.log deals with session level things, but you want to
> exclude object-level things. Try:
>
> create role skip_pguadit;
> alter user <batchuser> set pgaudit.role = 'skip_pgaudit';
>
>
> Cheers,
> Greg
>
> --
> Crunchy Data - https://www.crunchydata.com
> Enterprise Postgres Software Products & Tech Support
>
>

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Using pgAudit to audit interesting tables for all users except for batch user?
  In-Reply-To: <CAMon-aSyCvDk924RuP=BU5B4qsFAwJidWzQKmSEMgfL5KXKodQ@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox