From: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
---|---|
To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, Postgres JDBC <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: out of memory error on a delete command |
Date: | 2005-07-13 12:50:03 |
Message-ID: | 1121259003.3085.199.camel@coppola.muc.ecircle.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Ah, OK, I've misread your mail, so you say ignoring on delete triggers
is normal for TRUNCATE. Then all is fine with this one. I still need to
find out what have eaten the memory on that particular delete operation.
Cheers,
Csaba.
On Wed, 2005-07-13 at 14:23, Oliver Jowett wrote:
> Csaba Nagy wrote:
> > Well, I'm still at a guess what could cause the problem on the kind of
> > query I was executing (a "delete"). Kris' explanation with the deferred
> > trigger was the closest till now, except the trigger was not deferred,
> > and truncate still succeded with the "ON DELETE" trigger in place...
>
> Doesn't TRUNCATE explicitly ignore ON DELETE triggers?
>
> -O
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-07-13 13:50:29 | Re: out of memory error on a delete command |
Previous Message | Csaba Nagy | 2005-07-13 12:48:19 | Re: out of memory error on a delete command |