Re: from_collapse_limit vs. geqo_threshold

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Selena Deckelmann <selena(at)endpoint(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: from_collapse_limit vs. geqo_threshold
Date: 2009-06-02 03:46:39
Message-ID: 603c8f070906012046t5d741cflceda8b513f4a5d67@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 1, 2009 at 3:34 PM, Selena Deckelmann <selena(at)endpoint(dot)com> wrote:
> In the spirit of helping wrap-up 8.4 todo items...
> Robert Haas wrote:
>> For 8.4, I'd be happy to just improve the documentation.  I think this
>> sentence could just be deleted from the section on
>> from_collapse_limit:
> My vote would be to provide some information.
>
> Suggested revision of Robert's prose:
>
> Because genetic query optimization may be triggered, increasing
> from_collapse_limit should be considered relative to <xref
> linkend="guc-geqo-threshold">.

Here's my attempt.

...Robert

Attachment Content-Type Size
from-collapse-limit-doc.patch text/x-patch 1.2 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-06-02 03:50:06 Re: It's June 1; do you know where your release is?
Previous Message Ron Mayer 2009-06-02 03:30:49 Re: explain analyze rows=%.0f