pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Craig Ringer <craig@postnewspapers.com.au>
To: Eduardo Morras <emorras@s21sec.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Followup: vacuum'ing toast
Date: Thu, 05 Nov 2009 20:09:10 +0800
Message-ID: <4AF2C066.7070201@postnewspapers.com.au> (raw)
In-Reply-To: <4AF2BBB3.5030300@postnewspapers.com.au>
References: <ca24673e0911041552k70b4af34k6f689ab116fc8752@mail.gmail.com>
	<4AF229F5.201@2ndquadrant.com>
	<4AF24006.1010509@postnewspapers.com.au>
	<20091105090655.8EA085580B0@s21sec.com>
	<4AF2BBB3.5030300@postnewspapers.com.au>

Craig Ringer wrote:
> Eduardo Morras wrote:
>>> 3) Autocommit being disabled. At least when using Hibernate via JPA,
>>> that'll cause a major mess and would easily explain the issues you're
>>> seeing. Hibernate manages transactions explicitly when required, and
>>> expects autocommit to be off.
>> Excuse me but i don't understand this point. You say that the problem happens if Autocommit is disabled but that hibernates expects that Autocommit is disabled for a correct work. What's better then? Autocommit off for Hibernate or Autocommit On for the original poster problem. Can you explain it more?
> 
> Argh!
> 
> I'm really sorry. I meant that Hibernate expects autocommit to be
> _enabled_.

Some searching suggests that, indeed, the issue is that when using
Hibernate via JPA (Hibernate EntityManager) autocommit needs to be left
enabled.

For some reason there doesn't seem to be any explicit reference to
autocommit in the Hibernate EntityManager docs or the EJB3 spec. I can't
find anything but (numerous) forum posts and the like on this, so don't
take it as definitive.

--
Craig Ringer



view thread (8+ messages)  latest in thread

Message-ID: <4AF2C066.7070201@postnewspapers.com.au>
Permalink:  ../4AF2C066.7070201@postnewspapers.com.au/
Also on:    postgresql.org/message-id/4AF2C066.7070201@postnewspapers.com.au

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: craig@postnewspapers.com.au, emorras@s21sec.com
  Subject: Re: Followup: vacuum'ing toast
  In-Reply-To: <4AF2C066.7070201@postnewspapers.com.au>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox