DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk;
	h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=s+l4CPuWWq9vZS3xcdUT98/CpWRzWA1ePPj3WUUpx6scgnR5IMRbqAkQWlNkfhm+7+uslz+QMopGRBqGqxwEb9iqfqDhFtS1IG425ZHE9uzEbOKVXhMR1yiqLrpquF0UOtFTXPXMggFmlFAT4E4VSXFdqe7UoGxyiB6quTDoha8=;
Message-ID: <407434.55939.qm@web23607.mail.ird.yahoo.com>
Date: Thu, 19 Mar 2009 11:37:11 +0000 (GMT)
From: Glyn Astill <glynastill@yahoo.co.uk>
Reply-To: glynastill@yahoo.co.uk
Subject: Re: Prepared statement does not exist
To: pgsql-performance@postgresql.org, Nimesh Satam <nimesh.satam@gmail.com>,
	Nimesh Satam <nimesh.zedo@gmail.com>
In-Reply-To: <965aa3ed0903190432i77ca9b39v733663f92ef3e2d0@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


--- On Thu, 19/3/09, Nimesh Satam <nimesh.zedo@gmail.com> wrote:
>=20
> We are receving the following error in the postgres
> database logs:
>=20
> 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:=20
> 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:=20
> DEALLOCATE "S_4"
>=20
> 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 t=
o send the RESET ALL, this will deallocate the prepared statement. Then the=
 app is reconnecting to pgpool again and expecting the prepared statement t=
o still be available, which it will not be.=0A=0A=0A