Re: OOM-killer issue when updating a inheritance table which has large number of child tables - Mailing list pgsql-hackers

From David Fetter
Subject Re: OOM-killer issue when updating a inheritance table which has large number of child tables
Date
Msg-id 20150312133850.GA9579@fetter.org
Whole thread Raw
In response to OOM-killer issue when updating a inheritance table which has large number of child tables  (chenhj <chjischj@163.com>)
Responses Re: OOM-killer issue when updating a inheritance table which has large number of child tables  (chenhj <chjischj@163.com>)
List pgsql-hackers
On Thu, Mar 12, 2015 at 06:55:48PM +0800, chenhj wrote:
> Hi
> 
> In my test(PG9.3.4), i found when update a parent table which has a
> large number of child tables, the execute plan will consume lots of
> memory. And possibly cause OOM.

At the moment, partitioning into thousands of tables is not supported.

If you can reproduce the problem in PostgreSQL 9.3.6, or whichever
happens to be the most recent minor version by the time you do the
test, that will help.

Just generally, it helps to provide a complete test case which
reproduces the problem if at all possible.

Cheers,
David.
-- 
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david.fetter@gmail.com

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate



pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: pg_dump: CREATE TABLE + CREATE RULE vs. relreplident
Next
From: Tomas Vondra
Date:
Subject: Re: logical column ordering