From: | Marcelo Fernandes <marcefern7(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Logging queries executed by SPI_execute |
Date: | 2025-02-02 23:05:51 |
Message-ID: | CAM2F1VNmR59qggpGMAeGu34_DCj_7h-3mTE1VP=VRnKE+F5ZJA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
Thanks,
Marcelo.
From | Date | Subject | |
---|---|---|---|
Next Message | Marcelo Fernandes | 2025-02-03 01:36:13 | What is the story behind _SPI_PLAN_MAGIC? |
Previous Message | Tom Lane | 2025-02-02 21:56:59 | Re: Using Expanded Objects other than Arrays from plpgsql |