From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Issue in Improving the performance using prepared plan |
Date: | 2010-04-22 13:23:27 |
Message-ID: | cc9a511169eac933c1fdce7cf5fd8a40@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> I have written following trigger and trying to improve the performance by
> using prepared query everytime. I have used spi_prepare to prepare the query
> and $_SHARED global hash to persist the prepared plan but it doesn't seem to
> work. Though $query will be same always in following trigger, it prepares
> query everytime and never uses prepared plan.
> Could anyone tell me what's wrong going on?
Works fine for me. Note that your elog outputs are switched - you are claiming
the already prepared plan for the first time (if exists) and claiming the
first prepare when in fact it is reusing (else).
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201004220922
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAkvQTasACgkQvJuQZxSWSsiH1wCgwiuBRmjmGZ0WWKKD/6BwovhR
M7IAoME88RAuNAd0P1tH4ug/I8FFJ8Bj
=CG70
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Ben Chobot | 2010-04-22 14:56:17 | Re: How to read the execution Plan |
Previous Message | Glus Xof | 2010-04-22 13:07:21 | Re: Specific database vars, again... |