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 22819.1343145325@sss.pgh.pa.us
Whole thread Raw
In response to Re: Using ctid column changes plan drastically  (Thomas Kellerer <spam_eater@gmx.net>)
Responses Re: Using ctid column changes plan drastically
List pgsql-performance
Thomas Kellerer <spam_eater@gmx.net> writes:
> Tom Lane, 24.07.2012 16:23:
>> IIRC, type tid doesn't have any hash support.

> So the "bad" plan is expected?

Joins on tid columns just aren't supported very well at the moment.
Partly that's from lack of round tuits, and partly it's because it
doesn't seem all that wise to encourage people to use them.  There
are gotchas if any of the rows receive concurrent updates.

FWIW, it might be helpful to cast this as a NOT EXISTS rather than
NOT IN subquery.

            regards, tom lane

pgsql-performance by date:

Previous
From: Maciek Sakrejda
Date:
Subject: Re: Geoserver-PostGIS performance problems
Next
From: Thomas Kellerer
Date:
Subject: Re: Using ctid column changes plan drastically