From: Henrique Engelmann <henriqueengelmann@yahoo.com.br>
To: pgsql-performance@postgresql.org
Subject: Clustered tables and seqscan disabled
Date: Sat, 10 Dec 2005 15:29:37 +0000 (GMT)
Message-ID: <20051210152937.71243.qmail@web36410.mail.mud.yahoo.com> (raw)
Hi,
Sometime ago I worked in an implantation project that uses postgresql and I remember than the software house recommended us to use seqscan off...
I was not very sure, but I thought the best way should be set seqscan on and let postgresql choose the best access plan (index or seqscan). Even against the other team members I changed the configuration to seqscan on and the system didn´t worked anymore.
Studying better the reasons I verified that applications were expecting data in primary index order but with seqscan ON sometimes postgresql didn´t use an index and naturally data came without order.
I suggested changing the application and including a order by clause... but
the software house didn´t make it because they said the system was originally designed for oracle and they did not need to use the ORDER BY clause with Oracle and even so the data were always retrieved in primary index order.
I´m thinking with myself ... what kind of problems will they have in the future?
I think this kind of configuration is very dependent of clustered tables... Am I right?
Best regards!
Engelmann.
__________________________________________________
Faça ligações para outros computadores com o novo Yahoo! Messenger
http://br.beta.messenger.yahoo.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: henriqueengelmann@yahoo.com.br
Subject: Re: Clustered tables and seqscan disabled
In-Reply-To: <20051210152937.71243.qmail@web36410.mail.mud.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox