Re: Avoid long-running transactions in a long-running stored procedure?

From: Ow Mun Heng <Ow(dot)Mun(dot)Heng(at)wdc(dot)com>
To: josh(at)agliodbs(dot)com
Cc: pgsql-performance(at)postgresql(dot)org, David Crane <davidc(at)donorschoose(dot)org>
Subject: Re: Avoid long-running transactions in a long-running stored procedure?
Date: 2008-02-15 01:30:38
Message-ID: 1203039038.16694.39.camel@neuromancer.home.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


On Thu, 2008-02-14 at 17:29 -0800, Josh Berkus wrote:
> David,
>
> > Once per quarter, we need to load a lot of data, which causes many
> > updates across the database. We have an online transaction
> > processing-style application, which we really want to stay up during the
> > update job.
> However, you can write your stored procedures in an external language (like
> PL/Perl, PL/Ruby, PL/Java or PL/Python) and re-connect to your database in
> order to run several separate transactions. Several users are doing this
> for large ETL jobs.
>

I actually do it externally via a perl script even, and I'm breaking the
data down to even more than miniscule size.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message David Crane 2008-02-15 01:38:13 Re: Avoid long-running transactions in a long-runningstored procedure?
Previous Message Josh Berkus 2008-02-15 01:29:18 Re: Avoid long-running transactions in a long-running stored procedure?