pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gregory S. Williamson <gsw@globexplorer.com>
Cc: db@zigo.dhs.org
Cc: pgsql-performance@postgresql.org
Subject: Re: Horribly slow query/ sequential scan
Date: Tue, 09 Jan 2007 10:13:04 -0500
Message-ID: <7472.1168355584@sss.pgh.pa.us> (raw)
In-Reply-To: <71E37EF6B7DCC1499CEA0316A256832802B3EB8C@loki.wc.globexplorer.net>
References: <71E37EF6B7DCC1499CEA0316A256832802B3EB8A@loki.wc.globexplorer.net>
	<37813.192.121.104.48.1168346136.squirrel@zigo.dhs.org>
	<71E37EF6B7DCC1499CEA0316A256832802B3EB8C@loki.wc.globexplorer.net>

"Gregory S. Williamson" <gsw@globexplorer.com> writes:
> HAving burdened others with my foolishness too often, I hesitate to
> ask, but could someone either point me to a reference or explain what
> the difference might be ... I can see it with the eyes but I am having
> trouble understanding what Informix might have been doing to my (bad
> ?) SQL to "fix" the query.

Me too.  Does informix have anything EXPLAIN-like to show what it's
doing?

			regards, tom lane



view thread (11+ messages)  latest in thread

Message-ID: <7472.1168355584@sss.pgh.pa.us>
Permalink:  ../7472.1168355584@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/7472.1168355584@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, gsw@globexplorer.com, db@zigo.dhs.org
  Subject: Re: Horribly slow query/ sequential scan
  In-Reply-To: <7472.1168355584@sss.pgh.pa.us>

* 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