"Greg Sabino Mullane" writes:
> Perhaps you mean the discussion from
> July 6, 2009 started by Robert Haas? That was approximately 8000
> messages ago, and no consensus was reached that I could find.
Precisely.
> So I'd like to respectfully ask the hackers to consider raising the
> default value
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Tom Lane replied:
>> 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.
Tom, that
On Mon, Nov 16, 2009 at 10:42 PM, Tom Lane wrote:
> "Greg Sabino Mullane" 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
ridiculo
"Greg Sabino Mullane" 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.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Is there any chance we can raise the default geqo_threshold from
its current default of 12? This seems too low, as a modern Postgres
on modern hardware has no problem with 12 table joins. However, I have
seen geqo causing trouble for clients whe
