Re: Issue in Improving the performance using prepared plan

From: Jignesh Shah <jignesh(dot)shah1980(at)gmail(dot)com>
To: Greg Sabino Mullane <greg(at)turnstep(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Issue in Improving the performance using prepared plan
Date: 2010-04-23 07:30:28
Message-ID: q2kc11950271004230030ob1569409g5512907e832b4a6d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

:) I realized that. Thanks.

On Thu, Apr 22, 2010 at 6:53 PM, Greg Sabino Mullane <greg(at)turnstep(dot)com>wrote:

>
> -----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-----
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian von Bidder 2010-04-23 07:50:43 Re: Multicolumn primary key with null value
Previous Message Devrim GÜNDÜZ 2010-04-23 03:17:24 Re: I/O error during autovacuum