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

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: chenhj <chjischj(at)163(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: OOM-killer issue when updating a inheritance table which has large number of child tables
Date: 2015-03-12 20:00:31
Message-ID: 20150312200031.GK29780@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> chenhj <chjischj(at)163(dot)com> writes:
> > 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.
>
> See
> file:///net/sss1/home/postgres/pgsql/doc/src/sgml/html/ddl-partitioning.html#DDL-PARTITIONING-CAVEATS
>
> particularly the last paragraph.

Or perhaps, if you're on the Internet, this instead:

http://www.postgresql.org/docs/9.4/static/ddl-partitioning.html#DDL-PARTITIONING-CAVEATS

:)

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-03-12 20:07:33 Re: OOM-killer issue when updating a inheritance table which has large number of child tables
Previous Message Peter Eisentraut 2015-03-12 19:49:51 Re: forward vs backward slashes in msvc build code