Re: Using ctid column changes plan drastically - Mailing list pgsql-performance

From Tom Lane
Subject Re: Using ctid column changes plan drastically
Date
Msg-id 21308.1343139781@sss.pgh.pa.us
Whole thread Raw
In response to Using ctid column changes plan drastically  (Thomas Kellerer <spam_eater@gmx.net>)
Responses Re: Using ctid column changes plan drastically  (Thomas Kellerer <spam_eater@gmx.net>)
List pgsql-performance
Thomas Kellerer <spam_eater@gmx.net> writes:
> DELETE FROM dupes
> WHERE id NOT IN (SELECT min(b.id)
>                   FROM   dupes b
>                   GROUP BY first_name, last_Name
>                   HAVING count(*) > 1);

Doesn't that kill the non-duplicates too?

> Why does the usage of the CTID column change the plan so drastically?

IIRC, type tid doesn't have any hash support.

            regards, tom lane

pgsql-performance by date:

Previous
From: Ioannis Anagnostopoulos
Date:
Subject: Heavy inserts load wile querying...
Next
From: Torsten Zuehlsdorff
Date:
Subject: Re: ZFS vs. UFS