Re: Massive memory use for star query - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Massive memory use for star query
Date
Msg-id 25522.1302885781@sss.pgh.pa.us
Whole thread Raw
In response to Massive memory use for star query  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
Responses Re: Massive memory use for star query  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
List pgsql-bugs
Mark Kirkwood <mark.kirkwood@catalyst.net.nz> writes:
> I've recently seen examples of star-like queries using vast amounts of
> memory in one of our production systems. Here's a simplified example
> using synthetic data (see attached to generate if desired):

> SET geqo_threshold = 14;
> SET from_collapse_limit = 14;
> SET join_collapse_limit = 14;

Well, if you're going to do the above, you should be expecting the
planner to eat a lot of memory.  There is a reason why the default
values of those parameters are significantly lower than that ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Massive memory use for star query
Next
From: "Rikard Pavelic"
Date:
Subject: BUG #5982: recursive type crashes postgres