| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Matthias Apitz <guru(at)unixarea(dot)de> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Mysterious performance degradation in exceptional cases |
| Date: | 2022-09-14 14:23:48 |
| Message-ID: | 2675889.1663165428@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Matthias Apitz <guru(at)unixarea(dot)de> writes:
> To fulfill the search, the application server has to do some 100
> ESQL/C calls and all this should not take longer than 1-2 seconds, and
> normally it does not take longer. But, in some situations it takes
> longer than 180 seconds, in 10% of the cases. The other 90% are below 2 seconds,
> i.e. this is digital: Or 2 seconds, or more than 180 seconds, no values between.
I'm wondering about a plan change. Can you install auto_explain on
the server and capture info about the fast and slow cases?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2022-09-14 16:16:59 | understand pg_ndistinct type && Why with(autovacuum_enabled=off) some query estimate 100, some is 200. |
| Previous Message | Adrian Klaver | 2022-09-14 14:19:31 | Re: Mysterious performance degradation in exceptional cases |