From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Dawid Kuroczko <qnex42@gmail.com>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Planner doesn't look at LIMIT?
Date: Fri, 22 Jul 2005 14:06:17 -0400
Message-ID: <7214.1122055577@sss.pgh.pa.us> (raw)
In-Reply-To: <1122053518.21502.180.camel@localhost.localdomain>
References: <758d5e7f0507220210bfa4978@mail.gmail.com>
<29473.1122043197@sss.pgh.pa.us>
<6440.1122049220@sss.pgh.pa.us>
<1122053518.21502.180.camel@localhost.localdomain>
Simon Riggs <simon@2ndquadrant.com> writes:
> Looks good. I think it explains a few other wierd perf reports also.
Could be. I went back to look at Sam Mason's report about three weeks
ago, and it definitely seems to explain his issue. The "fuzzy cost
comparison" logic is new in 8.0 so it hasn't had all that much
testing...
regards, tom lane
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, simon@2ndquadrant.com, qnex42@gmail.com, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Planner doesn't look at LIMIT?
In-Reply-To: <7214.1122055577@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