On 5/11/2009 10:28 PM, Greg Smith wrote:
> Craig Ringer wrote:
>> Hibernate is pretty well behaved with transaction management. In fact,
>> it's downright nuts about keeping transactions open for as short a
>> period of time as possible. It even implements its own row-versioning
>> based optimistic
Greg Smith wrote:
> The biggest downside of [MVCC] is that if you have an old client
> lingering around, things that happened in the database after it started
> can't be cleaned up.
Just to clarify for readers: Idle clients aren't generally an issue.
It's only clients that are idle with an open t
Dave Crooke wrote:
Since the Jackrabbit tables are in the same namespace / user / schema
as ours, am I right in thinking that this is effectively blocking the
entire auto-vaccum system from doing anything at all?
Yes, but the problem is actually broader than that: it wouldn't matter
if it wa
Thanks folks for the quick replies.
1. There is one transaction, connected from the JVM, that is showing
"IDLE in transaction" this appears to be a leftover from
Hibernate looking at the schema metadata. It's Apache Jackrabbit, not
our own code:
hyper9test_1_6=# select c.relname, l.* from pg
