On Mon, Sep 12, 2022 at 05:34:37PM +0100, Matheus Martin wrote:
> Understood. I have run a prepared statement with the query in question
> through `psql` and JIT was not used (see plan below), however please note
> that the long response times were never reproducible from `psql`, they only
> happen
Understood. I have run a prepared statement with the query in question
through `psql` and JIT was not used (see plan below), however please note
that the long response times were never reproducible from `psql`, they only
happen from our JDBC application.
QUER
On Thu, Sep 8, 2022 at 1:18 PM Matheus Martin
wrote:
> We do have JIT enabled `jit=on` with `jit_above_cost=10`.
>
> I am sorry but I don't quite understand what role JIT plays in
> this situation with `auto_explain`. Could you please elaborate on that?
>
>
In your log - time spent during the
We do have JIT enabled `jit=on` with `jit_above_cost=10`.
I am sorry but I don't quite understand what role JIT plays in
this situation with `auto_explain`. Could you please elaborate on that?
On Tue, 6 Sept 2022 at 00:29, Maxim Boguk wrote:
>
>
> On Tue, Aug 30, 2022 at 1:38 PM Matheus Mar
On Tue, Aug 30, 2022 at 1:38 PM Matheus Martin <
matheus.mar...@voidbridge.com> wrote:
> Our Postgres recently started reporting considerably different execution
> times for the same query. When executed from our JDBC application the
> Postgres logs report an average execution time of 1500 ms bu
`auto_explain.log_min_duration` is set to 500 ms.
On Mon, 5 Sept 2022 at 12:35, Peter J. Holzer wrote:
> On 2022-09-02 10:58:58 +0100, Matheus Martin wrote:
> > Yes, we do see some plans logged by the auto_explain. We couldn't find a
> > `auto_explain.log_min_duration_statements` setting
>
> Th
On 2022-09-02 10:58:58 +0100, Matheus Martin wrote:
> Yes, we do see some plans logged by the auto_explain. We couldn't find a
> `auto_explain.log_min_duration_statements` setting
This is weird as the documentation says:
| Note that the default behavior is to do nothing, so you must set at
| leas
Yes, we do see some plans logged by the auto_explain. We couldn't find a
`auto_explain.log_min_duration_statements` setting but
`log_min_duration_statement` as in
https://www.postgresql.org/docs/current/runtime-config-logging.html is set
to 100 ms.
Unfortunately, due to the amount of traffic we ha
Hi,
On Thu, Sep 01, 2022 at 08:20:13PM +0100, Matheus Martin wrote:
> We tried running the prepared statement six times as suggested but wasn't
> still able to recreate the original problem.
>
> Perhaps more concerning/relevant is that we have not found any explanation
> to why the explain plan i
We tried running the prepared statement six times as suggested but wasn't
still able to recreate the original problem.
Perhaps more concerning/relevant is that we have not found any explanation
to why the explain plan is not being logged by `auto_explain`. Could this
be a bug? Shall we report it?
Alvaro Herrera writes:
> On 2022-Aug-30, Matheus Martin wrote:
>> Good idea on using an actual prepared statement but unfortunately it didn't
>> produce any different result.
> I should have also mentioned to try the EXPLAIN EXECUTE six times and
> see if the last one produces a different plan.
On 2022-Aug-30, Matheus Martin wrote:
> Good idea on using an actual prepared statement but unfortunately it didn't
> produce any different result.
I should have also mentioned to try the EXPLAIN EXECUTE six times and
see if the last one produces a different plan. That's when it switches
from pl
The threshold for `auto_explain` was changed to 500 ms and explain plans
are still not being logged.
On Tue, 30 Aug 2022 at 13:30, Julien Rouhaud wrote:
> Hi,
>
> On Tue, Aug 30, 2022 at 01:16:43PM +0200, Alvaro Herrera wrote:
> > On 2022-Aug-30, Matheus Martin wrote:
> >
> > > Our Postgres rece
Good idea on using an actual prepared statement but unfortunately it didn't
produce any different result.
Could you please elaborate a bit on your advice concerning
ExecutorEnd/PortalCleanup? I am afraid it doesn't mean much to me.
On Tue, 30 Aug 2022 at 12:16, Alvaro Herrera
wrote:
> On 2022-A
Hi,
On Tue, Aug 30, 2022 at 01:16:43PM +0200, Alvaro Herrera wrote:
> On 2022-Aug-30, Matheus Martin wrote:
>
> > Our Postgres recently started reporting considerably different
> > execution times for the same query. When executed from our JDBC
> > application the Postgres logs report an average
On 2022-Aug-30, Matheus Martin wrote:
> Our Postgres recently started reporting considerably different
> execution times for the same query. When executed from our JDBC
> application the Postgres logs report an average execution time of 1500
> ms but when the query is manually executed through `ps
Our Postgres recently started reporting considerably different
execution times for the same query. When executed from our JDBC
application the Postgres logs report an average execution time of 1500
ms but when the query is manually executed through `psql` it doesn't
take longer than 50 ms.
With a
17 matches
Mail list logo
