pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: jboes@nexcerpt.com
Cc: pgsql-sql@postgresql.org
Subject: Re: Long-running DELETE
Date: Wed, 16 Jan 2002 00:42:05 -0500
Message-ID: <7540.1011159725@sss.pgh.pa.us> (raw)
In-Reply-To: <d40a65a1.0201151102.218752c@posting.google.com>
References: <d40a65a1.0201151102.218752c@posting.google.com>

jboes@nexcerpt.com (Jeff Boes) writes:
> I've turned off every trigger in the database:

> update pg_triggers set tgenabled=false;

AFAIR, tgenabled isn't really supported; it's not tested for AFTER
triggers, which is what foreign keys use.  Your debug trace certainly
shows that the FK triggers are still live.

pg_dump knows how to disable triggers for real; I think it involves
setting pg_class.reltriggers to zero.

			regards, tom lane



view thread (5+ messages)  latest in thread

Message-ID: <7540.1011159725@sss.pgh.pa.us>
Permalink:  ../7540.1011159725@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/7540.1011159725@sss.pgh.pa.us

 · 

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-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, jboes@nexcerpt.com
  Subject: Re: Long-running DELETE
  In-Reply-To: <7540.1011159725@sss.pgh.pa.us>

* 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