using COPY and PARTITON

I believe triggers can do it.

thanks for reply

I am using rules with libpq instead of triggers now.
When INSERT was used, it was possible to insert it in CHILD TABLE well.
However, if COPY is used, it is possible to insert it only in PARENT TABLE.
Can triggers be used with libpq?
And, if trigger is used, can it straighten out that problem?

JM CHAE

Scott Marlowe-2 wrote:

I believe triggers can do it.

On Sun, Aug 9, 2009 at 11:15 PM, cjm1010<cjm1010@naver.com> wrote:

hi~

I want to insert DATA by using the COPY making PARTITON TABLE.  By the
way,
DATA is inserted only in PARENT TABLE.
Can DATA be inserted in CHILD TABLE by using the COPY?

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

--
View this message in context: http://www.nabble.com/using-COPY-and-PARTITON-tp24894446p24895140.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

Hi,

I'd recommend coping directly to child tables (partitions). It's much
faster.

Regards,
foo

Scott Marlowe wrote:

On Mon, Aug 10, 2009 at 12:58 AM, cjm1010<cjm1010@naver.com> wrote:

thanks for reply

I am using rules with libpq instead of triggers now.
When INSERT was used, it was possible to insert it in CHILD TABLE well.
However, if COPY is used, it is possible to insert it only in PARENT TABLE.
Can triggers be used with libpq?
And, if trigger is used, can it straighten out that problem?

Yep, triggers work just fine with libpq (if they didn't FK constraints
wouldn't work). I switched from rules to triggers a while back for my
reporting / stats database and they work a charm.