Hello Matthew, hello Tom,
thanks for your reply.
...and yes, the hint with the newly created index solved the problem.
kind regards...GERD...
Tom Lane wrote:
> =?ISO-8859-2?Q?Gerd_K=F6nig?= writes:
>> I'm quite sure that the difference from 94ms (explain of the delete
>> statement)
>> to 24s (
=?ISO-8859-2?Q?Gerd_K=F6nig?= writes:
> I'm quite sure that the difference from 94ms (explain of the delete statement)
> to 24s (duration in the trigger) is not only due to some overhead in trigger
> handling...but I've no idea what else we can check..?!?
There are two possible explanations for t
On Thu, 1 Oct 2009, Gerd König wrote:
Trigger NotReceivedTransport_Delete: time=24658.394 calls=1
Yeah, it's pretty obvious this is the problem.
explain analyze DELETE FROM "NotReceivedTransport" WHERE
"SId" = 11479 AND "CId" = 11479 AND
"ShipperTransportNumber" = '100432';
Hello,
we're currently facing long running insert statements with durations ~15sec (far
too long...) and I've no idea what's the reason for this issue.
An "explain analyze" of the insert statement tells me:
SNIP #
begin;
BEGIN
t
