Re: Using ctid column changes plan drastically

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thomas Kellerer <spam_eater@xxxxxxx> 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

-- 
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance


[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux