pg.ddx.io pgsql-performance@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: Tarcizio Bini <tarcizioab@c3sl.ufpr.br>
Cc: pgsql-performance@postgresql.org
Subject: Re: GEQO Benchmark
Date: Wed, 28 May 2008 17:52:40 +0100
Message-ID: <1211993560.4489.583.camel@ebony.site> (raw)
In-Reply-To: <461a87490805280913ha5bbc90w63db53787ced2adf@mail.gmail.com>
References: <55311.200.17.202.126.1211982648.squirrel@webmail.inf.ufpr.br>
<27530.1211983350@sss.pgh.pa.us>
<461a87490805280913ha5bbc90w63db53787ced2adf@mail.gmail.com>
On Wed, 2008-05-28 at 13:13 -0300, Tarcizio Bini wrote:
> Of course, the geqo_threshold can be changed so that the geqo be
> performed in queries that have less than 12 tables. However, we aim to
> test the GEQO algorithm in conditions where the standard algorithm
> (dynamic programming) has a high cost to calculate the query plan.
My understanding is the GEQO cannot arrive at a better plan than the
standard optimizer, so unless you wish to measure planning time there
isn't much to test. What is the quality of the plans it generates? Well
that varies according to the input; sometimes it gets the right plan,
other times it doesn't get close.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
view thread (5+ messages) latest in thread
Message-ID: <1211993560.4489.583.camel@ebony.site> Permalink: ../1211993560.4489.583.camel@ebony.site/ Also on: postgresql.org/message-id/1211993560.4489.583.camel@ebony.site ·
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: simon@2ndquadrant.com, tarcizioab@c3sl.ufpr.br Subject: Re: GEQO Benchmark In-Reply-To: <1211993560.4489.583.camel@ebony.site> * 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