Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Mon, 22 Jun 2009 12:53:40 +0300
- Message-id: <4A3F54A4.6040204@enterprisedb.com> <text/plain>
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
- References:
- Prev by Date: Re: Queries very slow and memory consumption too high
- Next by Date: Re: Queries very slow and memory consumption too high
- Previous by thread: Re: prepared transaction with identifier "1197822575_XAAAAAAAAABHVE1JRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==_AQAAAAAAAABHVE1JRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==" does not ex
- Next by thread: org.postgresql.util.PSQLException: ERROR: operator does not exist: character varying = integer
- Indexes: