Heikki Linnakangas <heikki@enterprisedb.com> writes:
> Do we consider committing a transaction from another database a feature,
> and fix NOTIFY/LISTEN, or should COMMIT PREPARED throw an error if
> you're not connected to the same database?
Hmm ... if we were sure NOTIFY were the only sore spot I'd say fix it,
but probably safer to refuse to commit, instead.
> Actually, I think we should completely separate the namespaces of the
> global transaction identifiers, so that you could use the same gid in
> two different databases without a conflict.
Really? They're supposed to be "global".
regards, tom lane