Re: Logging queries executed by SPI_execute

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Marcelo Fernandes <marcefern7(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Logging queries executed by SPI_execute
Date: 2025-02-04 05:06:55
Message-ID: CAFj8pRAZWSDyw9PzcU7Ju=2UbqZEsJqC=EECwFDk_-g+6qR_pw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

út 4. 2. 2025 v 5:09 odesílatel Marcelo Fernandes <marcefern7(at)gmail(dot)com>
napsal:

> On Mon, Feb 3, 2025 at 6:46 PM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
> > The queries executed by SPI are never executed on the top level. These
> queries are marked as nested.
> >
> > So you need to use auto_explain
> https://www.postgresql.org/docs/current/auto-explain.html with active
> auto_explain.log_nested_statements
>
> Thanks Pavel, I have tried that but however couldn't succeed.
>
> I have added this to my postgres.conf file:
>
> session_preload_libraries = 'auto_explain'
> auto_explain.log_nested_statements = true
>

you are missing setting auto_explain.log_min_duration

>
> After running pg_repack, which calls SPI_execute* functions, I can't
> really see
> those functions being propagated to the logs.
>
> I have a workaround in place, which is to add elog calls such as
>
> elog(LOG, "...")
>
> to capture the queries. But of course, ideally a postgres.conf setting
> would be
> more handy.
>
> Best,
> Marcelo
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Borisov 2025-02-04 11:54:52 Re: Using Expanded Objects other than Arrays from plpgsql
Previous Message Marcelo Fernandes 2025-02-04 04:08:48 Re: Logging queries executed by SPI_execute