Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: OOM Errors as a result of table inheritance and a bad plan(?)
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Arctic Toucan <arctic_toucan(at)hotmail(dot)com>
- Cc: pgsql-performance(at)postgresql(dot)org
- Subject: Re: OOM Errors as a result of table inheritance and a bad plan(?)
- Date: Fri, 28 Sep 2007 16:56:49 -0400
Arctic Toucan <arctic_toucan(at)hotmail(dot)com> writes: > -- Is there something magical about the hash aggregate estimate of 200 rows? Yeah, it's the default :-( > Is this a bug, or some subtlety of the Postgres query planner? It's an, um, known deficiency --- the planner hasn't got any idea how to construct aggregated statistics for an inheritance tree. regards, tom lane
- References:
- OOM Errors as a result of table inheritance and a bad plan(?)
- From: Arctic Toucan
- OOM Errors as a result of table inheritance and a bad plan(?)
- Prev by Date: Re: Non-blocking vacuum full
- Next by Date: Re: Non-blocking vacuum full
- Previous by thread: OOM Errors as a result of table inheritance and a bad plan(?)
- Next by thread: Non-blocking vacuum full
- Indexes: