| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Jessica Holle <jessica(dot)holle(at)vit(dot)de>, Pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Performance of SELECT directly and from application |
| Date: | 2020-06-24 06:14:31 |
| Message-ID: | 9dda6f8fa24bb80c7456a8439cba0b4adf2b8ae4.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, 2020-06-24 at 07:00 +0200, Jessica Holle wrote:
> we use PostgreSQL 12.3.1 and have a little bit trouble with performance.
> When the statement comes from the application (wildfly) duration is
> about 24982.819 ms. When I do the statement directly with psql duration
> is 967.773 ms.
> Duration from Wildfly is known becaue we use in postgresql.conf
> "log_min_duration_statement = 5000". There I see, that from application
> are 3 variables used.
> Is there any idea why this can happen or a hint to solve this issue?
Try using "auto_explain" to get EXPLAIN (ANALYZE, BUFFERS) output for the slow
execution. The comparison of these two execution plans would be instructive.
Does the application set any parameters? Does it use a cursor?
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dbatoCloud Solution | 2020-06-24 06:38:42 | Re: Performance of SELECT directly and from application |
| Previous Message | Jessica Holle | 2020-06-24 05:00:43 | Performance of SELECT directly and from application |