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
--- On Fri, 20/3/09, Nimesh Satam nimesh.z...@gmail.com wrote:
From: Nimesh Satam nimesh.z...@gmail.com
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
Hi,
I am not sure if sending this to the right place. I did try to get the
answer from pgpool mailing list but no luck . Would appreciate if someone
can help here.
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
--- On Thu, 19/3/09, Nimesh Satam nimesh.z...@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
