Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 8FDC663480D for ; Fri, 20 Mar 2009 06:04:09 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 97129-02 for ; Fri, 20 Mar 2009 06:03:59 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by mail.postgresql.org (Postfix) with ESMTP id 6B72C6335CF for ; Fri, 20 Mar 2009 06:04:00 -0300 (ADT) Received: by rv-out-0506.google.com with SMTP id l9so991041rvb.43 for ; Fri, 20 Mar 2009 02:03:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=FEmv+1/eg+uSoeGjpp4+peXyxNcUjlVGQz+UvjjG3V8=; b=C/AOGez2TCX8/bHdreZbcHEPraK4cXfs5ZKTE4TK27/8G5/CHHu15jFpBg2tsWlWP9 ikcG3pQEf5PB4hvoFHVyziQXFdtY9xu/YgBbqIeqg+nEVmxng4fNXQIOgaOZrgS2c10R dxFlRz1eDrO8U1gpUz9XLp7oWJqN94LIxRkcM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=q4xsC10YaEf0GnriEWUDFpsUfrLd1+miDGSgLgn4Sd/kQ/wrtKMK4vbc+VjT5foAAT LdYUyupoakyYg/ofE3SYvUTxLD1fa7Htvx9TOTM/Kj7+7FhO5713KCyoeO/kTZTqKld6 f5AmYw3AUnlseXwN6c0sBz3nSPvpuNUAbqHbE= MIME-Version: 1.0 Received: by 10.142.186.9 with SMTP id j9mr1391228wff.5.1237539838405; Fri, 20 Mar 2009 02:03:58 -0700 (PDT) In-Reply-To: <407434.55939.qm@web23607.mail.ird.yahoo.com> References: <965aa3ed0903190432i77ca9b39v733663f92ef3e2d0@mail.gmail.com> <407434.55939.qm@web23607.mail.ird.yahoo.com> Date: Fri, 20 Mar 2009 14:33:58 +0530 Message-ID: <965aa3ed0903200203w75bd3b96ofdf5b080dbbdd4c2@mail.gmail.com> Subject: Re: Prepared statement does not exist From: Nimesh Satam To: glynastill@yahoo.co.uk Cc: pgsql-performance@postgresql.org, Nimesh Satam Content-Type: multipart/alternative; boundary=000e0cd28d7676abff046589328b X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200903/284 X-Sequence-Number: 33206 --000e0cd28d7676abff046589328b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Glyn Astill, Thank for your reply. But can you confirm on this? As what I see from the logs, its pgpool which is trying to deallocate the prepared statement and not the application. The application just disconnects and not tyring to use the same connection. Regards, Nimesh. On Thu, Mar 19, 2009 at 5:07 PM, Glyn Astill wrote: > > > > > --- On Thu, 19/3/09, Nimesh Satam wrote: > > > > We are receving the following error in the postgres > > database logs: > > > > 2009-03-19 02:14:20 PDT [2547]: [79-1] LOG: duration: > > 0.039 ms statement: > > RESET ALL > > 2009-03-19 02:14:20 PDT [2547]: [80-1] LOG: duration: > > 0.027 ms statement: > > SET SESSION AUTHORIZATION DEFAULT > > 2009-03-19 02:14:20 PDT [2547]: [81-1] ERROR: prepared > > statement "S_1" does > > not exist > > 2009-03-19 02:14:20 PDT [2547]: [82-1] STATEMENT: > > DEALLOCATE "S_1" > > 2009-03-19 02:14:20 PDT [2547]: [83-1] ERROR: prepared > > statement "S_4" does > > not exist > > 2009-03-19 02:14:20 PDT [2547]: [84-1] STATEMENT: > > DEALLOCATE "S_4" > > > > We receive this errors when we start connecting the java > > application > > thorugh pgpool. What causes this problem and how can it be > > avoided? > > Looks like your app is dissconnecting from pgpool which is causing pgpool > to send the RESET ALL, this will deallocate the prepared statement. Then the > app is reconnecting to pgpool again and expecting the prepared statement to > still be available, which it will not be. > > > > --000e0cd28d7676abff046589328b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Glyn Astill,

Thank for your reply. But can you confirm on this? As what I see fromthe logs, its pgpool which is trying to deallocate the prepared
stateme= nt and not the application. The application just disconnects
and not tyr= ing to use the same connection.

Regards,
Nimesh.

On Thu, Mar 19, 2009 at 5:07 PM, Glyn Astill <glynastill@yah= oo.co.uk> wrote:




--- On Thu, 19/3/09, Nimesh Satam <nimesh.zedo@gmail.com> wrote:<= br>>
> We are receving the following error in the postgres
>= database logs:
>
> 2009-03-19 02:14:20 PDT [2547]: [79-1] LOG: =A0duration:
&g= t; 0.039 ms =A0statement:
> RESET ALL
> 2009-03-19 02:14:20 PDT= [2547]: [80-1] LOG: =A0duration:
> 0.027 ms =A0statement:
> SE= T SESSION AUTHORIZATION DEFAULT
> 2009-03-19 02:14:20 PDT [2547]: [81-1] ERROR: =A0prepared
> stat= ement "S_1" does
> not exist
> 2009-03-19 02:14:20 PD= T [2547]: [82-1] STATEMENT:
> DEALLOCATE "S_1"
> 2009= -03-19 02:14:20 PDT [2547]: [83-1] ERROR: =A0prepared
> statement "S_4" does
> not exist
> 2009-03-19 02= :14:20 PDT [2547]: [84-1] STATEMENT:
> DEALLOCATE "S_4"
= >
> We receive this errors when we start connecting the java
> application
> thorugh pgpool. What causes this problem and how c= an it be
> avoided?

Looks like your app is dissconnectin= g from pgpool which is causing pgpool to send the RESET ALL, this will deal= locate the prepared statement. Then the app is reconnecting to pgpool again= and expecting the prepared statement to still be available, which it will = not be.




--000e0cd28d7676abff046589328b--