Re: Raising the geqo_threshold default - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Raising the geqo_threshold default
Date
Msg-id 603c8f070911162021p479ece60o2c98b58a1a64f54c@mail.gmail.com
Whole thread Raw
In response to Re: Raising the geqo_threshold default  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Nov 16, 2009 at 10:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Greg Sabino Mullane" <greg@turnstep.com> writes:
>> Is there any chance we can raise the default geqo_threshold from
>> its current default of 12?
>
> We were over that just a few months ago.

Yeah.  I think we need to see if we can do something about the
ridiculous amount of memory that the standard planner consumes for
large join problems.  I would like to look into this problem, too,
which might be related, but have not had time:

http://archives.postgresql.org/pgsql-hackers/2009-11/msg00328.php

...Robert


pgsql-hackers by date:

Previous
From: Alex Hunsaker
Date:
Subject: Re: sgml and "empty" closing tags
Next
From: Robert Haas
Date:
Subject: Re: sgml and "empty" closing tags