Re: Partitioning option for COPY - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Partitioning option for COPY
Date
Msg-id 603c8f070911251528rd254525t4c13e05621a571e@mail.gmail.com
Whole thread Raw
In response to Re: Partitioning option for COPY  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Nov 25, 2009 at 11:30 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> It seems like the easiest way to resolve this without weird corner
> cases is to say that we fire triggers belonging to the parent table.
> The individual partition child tables either shouldn't have triggers
> at all, or we should restrict the cases in which those are considered
> applicable.
>
> As an example, what are you going to do with statement-level triggers?
> Fire them for *every* child whether it receives a row or not?  Doesn't
> seem like the right thing.

Just the tables that get a row?  I don't know, your way may be best,
but it seems like tables on individual partitions might be useful in
some situations.

> Again, this solution presupposes an explicit concept of partitioned
> tables within the system...

...Robert


pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: Partitioning option for COPY
Next
From: Jeff Davis
Date:
Subject: Re: operator exclusion constraints