Re: tidscan not work ? Pg 8.4.5 + WinXP - Mailing list pgsql-performance

From Kevin Grittner
Subject Re: tidscan not work ? Pg 8.4.5 + WinXP
Date
Msg-id 4CF4D5760200002500037F7D@gw.wicourts.gov
Whole thread Raw
In response to tidscan not work ? Pg 8.4.5 + WinXP  (pasman pasmański <pasman.p@gmail.com>)
Responses Re: tidscan not work ? Pg 8.4.5 + WinXP  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
pasman pasma*ski<pasman.p@gmail.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:

http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server

-Kevin

pgsql-performance by date:

Previous
From: Mladen Gogala
Date:
Subject: Re: SELECT INTO large FKyed table is slow
Next
From: Tom Lane
Date:
Subject: Re: tidscan not work ? Pg 8.4.5 + WinXP