From: | Emmanuel Cecchet <manu(at)asterdata(dot)com> |
---|---|
To: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
Cc: | Emmanuel Cecchet <Emmanuel(dot)Cecchet(at)asterdata(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Partitioning option for COPY |
Date: | 2009-11-26 15:16:57 |
Message-ID: | 4B0E9BE9.1020904@asterdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hannu Krosing wrote:
> After triggers can't change tuple, thus cant change routing.
>
An after trigger can always issue an update of the tuple but that should
be trapped by the regular mechanism that will deal with updates (when we
have it available).
>> Also the description omits the execution of before and after statement
>> triggers. While those can apply to the parent table (but the same
>> question about what happens if the after statement modifies routing
>> decision still applies), what does it mean in the case of COPY to have
>> statement triggers on the child tables?
>>
>
> What statement triggers do you mean ?
>
> I don't think we have ON COPY triggers ?
>
I mean
CREATE TRIGGER /name/ { BEFORE | AFTER } /event/
ON /table/ FOR EACH STATEMENT
Emmanuel
--
Emmanuel Cecchet
Aster Data
Web: http://www.asterdata.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-11-26 15:38:04 | Re: cvs chapters in our docs |
Previous Message | Andrew Dunstan | 2009-11-26 15:11:12 | Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION |