Re: Feature Request: Better handling of foreign keys in DELETE statements

From: Marti Raudsepp <marti(at)juffo(dot)org>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Daniel Migowski <dmigowski(at)ikoffice(dot)de>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Feature Request: Better handling of foreign keys in DELETE statements
Date: 2011-12-19 16:25:21
Message-ID: CABRT9RCezNAxTORS=QgmJLCeHTv1JcA0ysV0rufuNt+Dd24Hwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Dec 19, 2011 at 18:14, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> you can disable check per session if you need
> ALTER TABLE ... DISABLE TRIGGER ALL;

This is NOT a per-session command, this applies to all connections and
queries, and may allow incorrect data into the table. Don't do this!
(And it doesn't address the question anyway)

Regards,
Marti

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rick Pufky 2011-12-19 16:56:15 Re: recovery_target_timeline and multiple slave behavior when master fails
Previous Message Patrick Kevin McCaffrey 2011-12-19 16:20:07 Re: New User: PostgreSQL Setup - "The Program 'postgress' is needed by initdb but was not found in the same directory..."