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

Re: query plan wierdness?

From: Joel McGraw <jmcgraw(at)eldocomp(dot)com>
To: Guido Barosio <gbarosio(at)sinectis(dot)com(dot)ar>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: query plan wierdness?
Date: 2004-07-07 22:12:29
Message-ID: 7B3E33EF2A10A84185E3667F6B9A1B7825EE21@ECIEXCHANGE.eldocomp.com (view raw or flat)
Thread:
Lists: pgsql-performance
Well, you're kind of right.  I removed the limit, and now _both_
versions of the query perform a sequence scan!

Oh, I forgot to include in my original post: this is PostgreSQL 7.3.4
(on x86 Linux and sparc Solaris 6)

-Joel

-----Original Message-----
From: Guido Barosio [mailto:gbarosio(at)sinectis(dot)com(dot)ar] 
Sent: Wednesday, July 07, 2004 2:46 PM
To: Joel McGraw
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] query plan wierdness?

The limit is tricking you.
I guess a sequential scan is cheaper than an index scan with the limit
26 found there.

I am wrong?

Greets

-- 
-------------------------------------------
Guido Barosio
Buenos Aires, Argentina
-------------------------------------------

-- CONFIDENTIALITY NOTICE --

This message is intended for the sole use of the individual and entity to whom it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email, and delete the message. Thank you.

pgsql-performance by date

Next:From: Stephan SzaboDate: 2004-07-07 22:50:31
Subject: Re: query plan wierdness?
Previous:From: Guido BarosioDate: 2004-07-07 21:45:42
Subject: Re: query plan wierdness?

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