Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: TB-sized databases
- 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: Fri, 30 Nov 2007 12:31:01 +1300
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
- References:
- TB-sized databases
- From: Peter Koczan
- Re: TB-sized databases
- From: Pablo Alcaraz
- Re: TB-sized databases
- From: Stephen Cook
- Re: TB-sized databases
- From: Peter Koczan
- Re: TB-sized databases
- From: Simon Riggs
- Re: TB-sized databases
- From: Pablo Alcaraz
- Re: TB-sized databases
- From: Matthew
- Re: TB-sized databases
- From: Bill Moran
- Re: TB-sized databases
- From: Csaba Nagy
- Re: TB-sized databases
- From: Simon Riggs
- TB-sized databases
- Prev by Date: Re: clear pg_stats
- Next by Date: Re: Configuring a Large RAM PostgreSQL Server
- Previous by thread: Re: TB-sized databases
- Next by thread: Re: TB-sized databases
- Indexes: