Re: Logging queries executed by SPI_execute - Mailing list pgsql-general

From Pavel Stehule
Subject Re: Logging queries executed by SPI_execute
Date
Msg-id CAFj8pRAKZBhsFQVcmsfFfvEYgv0SeA7TWgjvLRtzCfdB6ws3JQ@mail.gmail.com
Whole thread Raw
In response to Logging queries executed by SPI_execute  (Marcelo Fernandes <marcefern7@gmail.com>)
Responses Re: Logging queries executed by SPI_execute
List pgsql-general
Hi

po 3. 2. 2025 v 0:06 odesílatel Marcelo Fernandes <marcefern7@gmail.com> napsal:
Hi there,

I have been trying to debug what queries an extension is firing. After reading
the code for the extension, I noticed that all the statements are fired via the
SPI interface, most specifically, using the SPI_execute* family of functions.

However, the problem is that these statements don't seem to feature in the
logfile. It has become a bit of a "dead end" for me to fully analyse what
queries are fired in the end.

My postgresql.conf is fairly simple, but I have added "log_statement = 'all'"
and thus was expecting to see information for these statements too.

Is there anything I am missing? Some configuration or perhaps another way to
find out about these statements?

It may not be relevant, but the extension I am having a look at is pg_repack if
anyone is interested. I am trying to get a deeper understanding of what the
function repack_apply does.

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

Regards

Pavel
 
Thanks,
Marcelo.


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: What is the story behind _SPI_PLAN_MAGIC?
Next
From: Marcelo Fernandes
Date:
Subject: Re: What is the story behind _SPI_PLAN_MAGIC?