Re: prepared transaction with identifier "1197822575_XAAAAAAAAABHVE1JRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==_AQAAAAAAAABHVE1JRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==" does not ex

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Dennis Brakhane <brakhane(at)googlemail(dot)com>
Cc: Ashish Jain <ashjain2(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: prepared transaction with identifier "1197822575_XAAAAAAAAABHVE1JRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==_AQAAAAAAAABHVE1JRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==" does not ex
Date: 2009-06-22 09:53:40
Message-ID: 4A3F54A4.6040204@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Dennis Brakhane wrote:
> Did you forget to modify the max_prepared_transactions setting in
> postgres' config?
> The default value of 5 is too small to be useful.

I wouldn't expect that to cause the error message Ashish reported.

(I don't have any better suggestions, though)

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Saurabh Dave 2009-06-23 01:48:05 Re: Queries very slow and memory consumption too high
Previous Message Albe Laurenz 2009-06-22 07:32:23 Re: Queries very slow and memory consumption too high