pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Merlin Moncure <mmoncure@gmail.com>
To: Sabin Coanda <sabin.coanda@deuromedia.ro>
Cc: pgsql-performance@postgresql.org
Subject: Re: long transaction
Date: Mon, 11 Aug 2008 15:03:10 -0400
Message-ID: <b42b73150808111203l14df2d2dicd4350f04d64e838@mail.gmail.com> (raw)
In-Reply-To: <g7onk7$12sj$1@news.hub.org>
References: <g5qd5o$1ot3$1@news.hub.org>
	<120621.32315.qm@web59503.mail.ac4.yahoo.com>
	<g7onk7$12sj$1@news.hub.org>

On Mon, Aug 11, 2008 at 2:53 AM, Sabin Coanda
<sabin.coanda@deuromedia.ro> wrote:
> No, I cannot use VACUUM inside the transaction, and it seems this is the
> problem, although autovacuum is set.
>
> However I checked the following scenario to find a solution. I call the
> 30000 statements without transaction. The performance it not changed. But
> when I add VACUUM command after each 20 statement set, I got the linear
> performance that I want. Unfortunatelly this is not possible inside a
> transaction.
>
> Do you know how could I solve my problem, keeping the 30000 statements
> inside a single transaction ?

long running transactions can be evil. is there a reason why this has
to run in a single transaction?

merlin



view thread (8+ messages)  latest in thread

Message-ID: <b42b73150808111203l14df2d2dicd4350f04d64e838@mail.gmail.com>
Permalink:  ../b42b73150808111203l14df2d2dicd4350f04d64e838@mail.gmail.com/
Also on:    postgresql.org/message-id/b42b73150808111203l14df2d2dicd4350f04d64e838@mail.gmail.com

 · 

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: mmoncure@gmail.com, sabin.coanda@deuromedia.ro
  Subject: Re: long transaction
  In-Reply-To: <b42b73150808111203l14df2d2dicd4350f04d64e838@mail.gmail.com>

* 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