Skip site navigation (1) Skip section navigation (2)

Re: JDBC/Stored procedure performance issue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: mlunnon(at)rwa-net(dot)co(dot)uk
Cc: mclister(at)zeesource(dot)net, pgsql-performance(at)postgresql(dot)org
Subject: Re: JDBC/Stored procedure performance issue
Date: 2008-01-29 18:08:50
Message-ID: 23231.1201630130@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
Matthew Lunnon <mlunnon(at)rwa-net(dot)co(dot)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

In response to

pgsql-performance by date

Next:From: Andrew SullivanDate: 2008-01-29 18:09:26
Subject: Re: analyze
Previous:From: Matthew LunnonDate: 2008-01-29 17:38:13
Subject: Re: Performance problems inside a stored procedure.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group