Skip site navigation (1) Skip section navigation (2)

Re: tidscan not work ? Pg 8.4.5 + WinXP

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: pasman pasma*ski <pasman(dot)p(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: tidscan not work ? Pg 8.4.5 + WinXP
Date: 2010-11-30 16:44:06
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
pasman pasma*ski<pasman(dot)p(at)gmail(dot)com> wrote:
> How to use tid scans?
Write a query where they are the fastest way to retrieve the data,
and make sure your PostgreSQL installation is properly configured.
> This below not works :-( Always is used merge join.
> SELECT * FROM test1 join test2 on(test1.ctid=test2.ct)
You're reading through the entirety of two tables matching rows
between them.  What makes you think random access would be faster
than sequential?  If all this data is cached, then maybe random
access could win, but you would need to configure your PostgreSQL to
expect that.
Have you read this page:

In response to


pgsql-performance by date

Next:From: Tom LaneDate: 2010-11-30 16:49:55
Subject: Re: tidscan not work ? Pg 8.4.5 + WinXP
Previous:From: Mladen GogalaDate: 2010-11-30 16:26:04
Subject: Re: SELECT INTO large FKyed table is slow

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group