At the moment, partitioning into thousands of tables is not supported.
Thank you for your reply. And thanks Tom Lane and Stephen Frost！
The following(with createsql.sql and update.sql as attachment) is my complete
test case. And i reproduced this problem in PostgreSQL 9.4.1 .
1)create
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.
For example:
create table maintb(id int,name char(10));
create table childtb_1 (CHECK ( id BETWEEN 1 AND 200))
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
chenhj chjis...@163.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
* Tom Lane (t...@sss.pgh.pa.us) wrote:
chenhj chjis...@163.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
Stephen Frost sfr...@snowman.net writes:
* Tom Lane (t...@sss.pgh.pa.us) wrote:
See
file:///net/sss1/home/postgres/pgsql/doc/src/sgml/html/ddl-partitioning.html#DDL-PARTITIONING-CAVEATS
Or perhaps, if you're on the Internet, this instead:
