Re: getting all constraint violations

Поиск
Список
Период
Сортировка
От Gauthier, Dave
Тема Re: getting all constraint violations
Дата
Msg-id 482E80323A35A54498B8B70FF2B879800458B887A1@azsmsx504.amr.corp.intel.com
обсуждение исходный текст
Ответ на Re: getting all constraint violations  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
I'm thinking more along the lines of creating a bunch of temp tables, each with one of the constraints.  Then, in a
loop,throw the record at each of these temp tables and collect up the violations.  

Exploring now hot to get the pieces I need from the metadata tables to do this.


-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Friday, May 21, 2010 3:10 PM
To: Gauthier, Dave
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] getting all constraint violations

"Gauthier, Dave" <dave.gauthier@intel.com> writes:
> Is there a way to temporarily suspend constraint checking for a particular constraint inside of the transaction, try
theinsert again, capture the next violation, then the next, etc... then rollback after all have been collected? 

You could do something like

    BEGIN;
    ALTER TABLE DROP CONSTRAINT ...
    INSERT ...
    ROLLBACK;

The major deficiency of this is that the ALTER TABLE would grab
exclusive lock on the table, so this doesn't scale if you need to
have several insertions happening in parallel.

            regards, tom lane

В списке pgsql-general по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: getting all constraint violations
Следующее
От: Andreas Schmitz
Дата:
Сообщение: Re: cleaning wal files from postgres