Re: prepared transaction with identifier "1197822575_XAAAAAAAAABHVE1JRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==_AQAAAAAAAABHVE1JRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==" does not ex - Mailing list pgsql-jdbc

From Heikki Linnakangas
Subject Re: prepared transaction with identifier "1197822575_XAAAAAAAAABHVE1JRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==_AQAAAAAAAABHVE1JRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==" does not ex
Date
Msg-id 4A3F54A4.6040204@enterprisedb.com
Whole thread Raw
In response to Re: prepared transaction with identifier "1197822575_XAAAAAAAAABHVE1JRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==_AQAAAAAAAABHVE1JRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==" does not ex  (Dennis Brakhane <brakhane@googlemail.com>)
List 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

pgsql-jdbc by date:

Previous
From: "Albe Laurenz"
Date:
Subject: Re: Queries very slow and memory consumption too high
Next
From: Saurabh Dave
Date:
Subject: Re: Queries very slow and memory consumption too high