Richard Broersma Jr <[EMAIL PROTECTED]> writes:
>> But I DELETE all conflicting those rows prior to the slow DELETE, just
>> so the FK check is never hit. Should I be looking at subverting the FK
>> check mechanism somehow? The necessary index would be huge, and
>> relevant only on this particula
> But I DELETE all conflicting those rows prior to the slow DELETE, just
> so the FK check is never hit. Should I be looking at subverting the FK
> check mechanism somehow? The necessary index would be huge, and
> relevant only on this particular operation which happens every few
> months, if tha
Tom Lane wrote:
> Bryce Nesbitt <[EMAIL PROTECTED]> writes:
>
>> I've got a DELETE FROM that seems to run forever, pegging the CPU at
>> 100%. I can't figure out why it's slow. Any clues?
>>
>
> Unindexed foreign key constraints pointing to this table, perhaps?
> EXPLAIN ANALYZE would giv
Bryce Nesbitt <[EMAIL PROTECTED]> writes:
> I've got a DELETE FROM that seems to run forever, pegging the CPU at
> 100%. I can't figure out why it's slow. Any clues?
Unindexed foreign key constraints pointing to this table, perhaps?
EXPLAIN ANALYZE would give a great deal more clue than plain EX