From: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Csaba Nagy <nagy(at)ecircle-ag(dot)com>, Bill Moran <wmoran(at)collaborativefusion(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: TB-sized databases |
Date: | 2007-11-29 23:31:01 |
Message-ID: | 474F4BB5.7090305@paradise.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Simon Riggs wrote:
> On Wed, 2007-11-28 at 14:48 +0100, Csaba Nagy wrote:
>
>
>> In fact an even more useful option would be to ask the planner to throw
>> error if the expected cost exceeds a certain threshold...
>>
>
> Well, I've suggested it before:
>
> statement_cost_limit on pgsql-hackers, 1 March 2006
>
> Would people like me to re-write and resubmit this patch for 8.4?
>
> Tom's previous concerns were along the lines of "How would know what to
> set it to?", given that the planner costs are mostly arbitrary numbers.
>
> Any bright ideas, or is it we want it and we don't care about the
> possible difficulties?
>
>
Knowing how to set it is a problem - but a possibly bigger one is that
monster query crippling your DW system, so I'd say lets have it.
Cheers
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2007-11-30 05:50:14 | Re: Configuring a Large RAM PostgreSQL Server |
Previous Message | Magnus Hagander | 2007-11-29 21:57:25 | Re: clear pg_stats |