John Papandriopoulos <dr(dot)jpap(at)gmail(dot)com> writes:
> I've recreated the same example with just one parent table, and 4096 child tables.
> SELECT query planning is lightning fast as before; DELETE and UPDATE cause my machine to swap.
> What's different about DELETE and UPDATE here?
Hmm. Rules? Triggers? You seem to be assuming the problem is at the
planner stage but I'm not sure you've proven that.
regards, tom lane
In response to
pgsql-performance by date
|Next:||From: Tom Lane||Date: 2010-12-04 16:59:58|
|Subject: Re: problem with from_collapse_limit and joined views |
|Previous:||From: Віталій Тимчишин||Date: 2010-12-04 15:32:16|
|Subject: Re: Slow query to get last created row using CURRVAL|