Re: Long-running DELETE

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Jeff Boes <jboes(at)nexcerpt(dot)com>
Cc: <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Long-running DELETE
Date: 2002-01-16 15:14:24
Message-ID: 20020116071240.U43837-100000@megazone23.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Wed, 16 Jan 2002, Jeff Boes wrote:

> On Tue, 15 Jan 2002 21:13:49 -0800 (PST)
> Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> wrote:
>
> >
> > On 15 Jan 2002, Jeff Boes wrote:
> >
> > > update pg_triggers set tgenabled=false;
> >
> > I don't think tgenabled works. You'll probably need to set reltriggers to
> > 0 on the pg_class row for the table (and then reset it to the correct
> > value afterwards).
> >
>
> I can't confirm that one, but I did find that things got a lot faster
> when I also did
>
> update pg_trigger
> set tgenabled=false,
> tgdeferrable=true,
> tginitdeferred=true
>
> for each of the associated triggers.

Hmm, that'd make the actual trigger calls wait till end of transaction.
If you were running the deletes in a transaction, that'd make the delete
parts go faster, but the commit should take a while.

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Stephan Szabo 2002-01-16 15:17:04 Re: limiting access to (through) views
Previous Message Glenn MacGregor 2002-01-16 14:47:21 limiting access to (through) views