From: Tom Lane <tgl@sss.pgh.pa.us>
To: mlunnon@rwa-net.co.uk
Cc: mclister@zeesource.net
Cc: pgsql-performance@postgresql.org
Subject: Re: JDBC/Stored procedure performance issue
Date: Tue, 29 Jan 2008 13:08:50 -0500
Message-ID: <23231.1201630130@sss.pgh.pa.us> (raw)
In-Reply-To: <479EFC21.60606@rwa-net.co.uk>
References: <018573B2-DC52-4B98-9AB6-1ACB953B0035@zeesource.net>
<6915.1201553513@sss.pgh.pa.us>
<479EFC21.60606@rwa-net.co.uk>
Matthew Lunnon <mlunnon@rwa-net.co.uk> writes:
> Is there any way to work out what plan the query is using in side the
> function? I think I have a similar problem with a query taking much
> longer from inside a function than it does as a select statement.
Standard approach is to PREPARE a statement that has parameters in the
same places where the function uses variables/parameters, and then use
EXPLAIN [ANALYZE] EXECUTE to test it.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, mlunnon@rwa-net.co.uk, mclister@zeesource.net
Subject: Re: JDBC/Stored procedure performance issue
In-Reply-To: <23231.1201630130@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox