Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: index vs. seq scan choice?
Date: Thu, 7 Jun 2007 15:21:14 -0700
Message-ID: 
 <8C5B026B51B6854CBE88121DBF097A86DEA6C5@ehost010-33.exch010.intermedia.net>
In-Reply-To: <4668804F.6090201@commandprompt.com>
Thread-Topic: [GENERAL] index vs. seq scan choice?
Thread-Index: AcepTs+SlHbhjrVJSe2iNu1p57l1zwAAeMBg
References: 
 <8C5B026B51B6854CBE88121DBF097A86C3A30D@ehost010-33.exch010.intermedia.net>
	<27828.1180055291@sss.pgh.pa.us>
	<8C5B026B51B6854CBE88121DBF097A86DEA6B4@ehost010-33.exch010.intermedia.net>
	<4668804F.6090201@commandprompt.com>
From: "George Pavlov" <gpavlov@mynewplace.com>
To: "Joshua D. Drake" <jd@commandprompt.com>
Cc: "Tom Lane" <tgl@sss.pgh.pa.us>,
	<pgsql-general@postgresql.org>

> From: Joshua D. Drake [mailto:jd@commandprompt.com]
>=20
> In those rare cases wouldn't it make more sense to just set=20
> enable_seqscan to off; run query; set enable_seqscan to on;

1. these cases are not that rare (to me);

2. setting enable_seqscan (in JDBC, say) from the application makes the
whole thing quite a mess (need to do a batch of statements: each query
wrapped in its enable/disable seq scan?) -- ideally, one would like to
issue mostly SQL statements, not config parameters from the application;

3. if this is the recommended suggestion on how to run queries then why
don't we just add HINTS to the system and be done with it...