Message-ID: <9dda6f8fa24bb80c7456a8439cba0b4adf2b8ae4.camel@cybertec.at>
Subject: Re: Performance of SELECT directly and from application
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Jessica Holle <jessica.holle@vit.de>, Pgsql-admin
	 <pgsql-admin@postgresql.org>
Date: Wed, 24 Jun 2020 08:14:31 +0200
In-Reply-To: <404eece7-44b3-bbb4-177a-ff955d10e7e6@vit.de>
References: <404eece7-44b3-bbb4-177a-ff955d10e7e6@vit.de>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.32.5 (3.32.5-1.fc30) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

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