Re: delete quite skip updated rows

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: delete quite skip updated rows
Date: 2009-03-27 14:43:53
Message-ID: 8676.1238165033@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> explain analyze signalise one deleted row, but this is not true

This is not a bug. The explain output tells you that one row was
found by the seqscan, which is true. It doesn't tell you whether
the delete machinery did anything with that row. The row could
be suppressed from deletion by a BEFORE DELETE trigger, or because
it was already updated in the current command (as is the case here).

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2009-03-27 14:44:00 Re: typedefs for indent
Previous Message Simon Riggs 2009-03-27 14:36:36 Re: New trigger option of pg_standby