Skip site navigation (1) Skip section navigation (2)

Re: A bunch of minor issues

From: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
To: "Dave Page" <dpage(at)postgresql(dot)org>
Cc: <pgadmin-hackers(at)postgresql(dot)org>,"Guillaume Lelarge" <guillaume(at)lelarge(dot)info>
Subject: Re: A bunch of minor issues
Date: 2007-09-26 11:14:51
Message-ID: 46FA3F2B.1060606@enterprisedb.com (view raw or flat)
Thread:
Lists: pgadmin-hackers
Dave Page wrote:
> Dave Page wrote:
>>> When trying to commit/rollback a prepared transaction in a database
>>> other than 'postgres', using the "server status" dialog, I always get
>>> this error message:
>>>
>>> ERROR:  prepared transaction belongs to another database
>>> HINT:  Connect to the database where the transaction was prepared to
>>> finish it.
>>>
>>> Apparently the "server status" always operates with the 'postgres'
>>> database...
>>
>> Will investigate and fix.
> 
> Seems this is only an issue with 8.3 Fix committed to SVN.

Really? <checks 8.2 source code>. No, that change was backpatched all
the way to 8.1 branch, which is the first release with 2PC. The check is
in src/backend/access/transam/twophase.c:

> 		/*
> 		 * Note: it probably would be possible to allow committing from another
> 		 * database; but at the moment NOTIFY is known not to work and there
> 		 * may be some other issues as well.  Hence disallow until someone
> 		 * gets motivated to make it work.
> 		 */
> 		if (MyDatabaseId != gxact->proc.databaseId)
> 			ereport(ERROR,
> 					(errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
> 					 errmsg("prepared transaction belongs to another database"),
> 					 errhint("Connect to the database where the transaction was prepared to finish it.")));

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

In response to

Responses

pgadmin-hackers by date

Next:From: Heikki LinnakangasDate: 2007-09-26 11:26:35
Subject: Re: A bunch of minor issues
Previous:From: Dave PageDate: 2007-09-26 11:10:47
Subject: Re: A bunch of minor issues

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group