From: Glyn Astill <glynastill@yahoo.co.uk>
To: pgsql-performance@postgresql.org, Nimesh Satam <nimesh.satam@gmail.com>
To: Nimesh Satam <nimesh.zedo@gmail.com>
Subject: Re: Prepared statement does not exist
Date: Thu, 19 Mar 2009 11:37:11 +0000 (GMT)
Message-ID: <407434.55939.qm@web23607.mail.ird.yahoo.com> (raw)
In-Reply-To: <965aa3ed0903190432i77ca9b39v733663f92ef3e2d0@mail.gmail.com>
--- On Thu, 19/3/09, Nimesh Satam <nimesh.zedo@gmail.com> 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: glynastill@yahoo.co.uk, nimesh.satam@gmail.com, nimesh.zedo@gmail.com
Subject: Re: Prepared statement does not exist
In-Reply-To: <407434.55939.qm@web23607.mail.ird.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox