Re: Issue in Improving the performance using prepared plan
От | Greg Sabino Mullane |
---|---|
Тема | Re: Issue in Improving the performance using prepared plan |
Дата | |
Msg-id | cc9a511169eac933c1fdce7cf5fd8a40@biglumber.com обсуждение исходный текст |
Ответ на | Issue in Improving the performance using prepared plan (Jignesh Shah <jignesh.shah1980@gmail.com>) |
Ответы |
Re: Issue in Improving the performance using prepared plan
|
Список | 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@turnstep.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-----
В списке pgsql-general по дате отправления: