Horton

Re: Partitioning option for COPY

Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>

View thread View on postgr.es
From: Itagaki Takahiro <itagaki.takahiro@oss.ntt.co.jp>
To: Emmanuel Cecchet <manu@asterdata.com>
Cc: Hannu Krosing <hannu@2ndQuadrant.com>, Robert Haas <robertmhaas@gmail.com>, Simon Riggs <simon@2ndquadrant.com>, Emmanuel Cecchet <Emmanuel.Cecchet@asterdata.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2009-11-25T02:16:14Z
Lists: pgsql-hackers 
Emmanuel Cecchet <manu@asterdata.com> wrote:

> I guess the problem of handling user triggers is still open.
> If we allow triggers on partitions, badly written logic could lead to 
> infinite loops in routing.

Infinite loops are not a partition-related problem, no?
We can also find infinite loops in user defined functions,
recursive queries, etc. I think the only thing we can do for it
is to *stop* loops instead of prevention, like max_stack_depth.

> With the current proposed implementation, would it be 
> possible to define a view using child tables?

No, if you mean using a partition-view. I'm thinking we are moving
our implementation of partitioning from view-based to built-in feature.
Do you have any use-cases that requires view-based partitioning?
Was the inheritance-based partitioning not enough for it?

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center