From: | Volkan YAZICI <yazicivo(at)ttmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Memory Problem |
Date: | 2008-07-03 07:49:18 |
Message-ID: | 87ej6bpfup.fsf@alamut.mobiliz.com.tr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
On Wed, 02 Jul 2008, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Are there any foreign keys referencing this table? If so, you're
> probably running out of memory for the list of pending trigger events
> (to verify that the FK constraint isn't violated by the delete).
>
> Allowing the triggers to fire individually would take forever anyway,
> so it might be best to drop the foreign key constraint(s) and then
> re-establish them after the delete.
Thanks for the warning. Temporarily disabling FKs did the job. I knew
the problem about triggers, but didn't expect same applies for FKs
also. I'm very suprised FKs cause memory exhaustion too.
Regards.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2008-07-03 07:52:33 | Re: Problem with roles and permissions |
Previous Message | Dave Page | 2008-07-03 07:42:10 | Re: pg_dump - lost synchronization with server: got message type "d", length 6036499 |