Date: Fri, 10 Sep 2021 10:42:55 +0200
From: hubert depesz lubaczewski <depesz@depesz.com>
Sender: depesz@depesz.com
To: Hotmail <crajac66@hotmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Is there anyway for non-superuser to log all sql statements at
 the session level?
Message-ID: <20210910084255.GB11352@depesz.com>
Reply-To: depesz@depesz.com
References: <16e9ff79-fe32-4d0d-be57-7c823744a793@Spark>
 <SJ0PR06MB76469C5B646B4551B6292DBFD7D59@SJ0PR06MB7646.namprd06.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <SJ0PR06MB76469C5B646B4551B6292DBFD7D59@SJ0PR06MB7646.namprd06.prod.outlook.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: 
 <https://www.postgresql.org/message-id/20210910084255.GB11352%40depesz.com>
Precedence: bulk

On Thu, Sep 09, 2021 at 05:30:55PM -0600, Hotmail wrote:
> We use liquibase to run migrations against our postgres 11 database.
> We run the migrations as an application user that does not have
> superuser permissions. Is there any workaround we could use that would
> allow us to capture the migration sql that is run by our application
> user? We want to capture all of the ddl as well as the dml run by the
> migration user. Since setting log_statement=all  at the session level
> isn’t possible unless the user is a superuser is there any other way
> to accomplish this task?

Sure. Make a security-definer function that changes the log_statement,
and grant privileges to call it to whoever you need.

Best regards,

depesz