Re: Using ctid column changes plan drastically

From: Thomas Kellerer <spam_eater(at)gmx(dot)net>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Using ctid column changes plan drastically
Date: 2012-07-24 16:32:09
Message-ID: jumim1$nq7$1@dough.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Tom Lane wrote on 24.07.2012 17:55:
> 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.

Thanks for the clarification. I will keep that in mind.

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

Hmm. How would you change that into an NOT EXISTS clause (so that one of the duplicates remains)
Everything I come up with is in fact slower than the NOT IN solution.

Regards
Thomas

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2012-07-24 17:12:46 Re: Using ctid column changes plan drastically
Previous Message Tom Lane 2012-07-24 15:55:25 Re: Using ctid column changes plan drastically