| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Raising the geqo_threshold default |
| Date: | 2009-11-17 04:21:21 |
| Message-ID: | 603c8f070911162021p479ece60o2c98b58a1a64f54c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 16, 2009 at 10:42 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Greg Sabino Mullane" <greg(at)turnstep(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-11-17 04:25:11 | Re: sgml and "empty" closing tags |
| Previous Message | Alex Hunsaker | 2009-11-17 03:54:45 | Re: sgml and "empty" closing tags |