| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | cjm1010 <cjm1010(at)naver(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: using COPY and PARTITON |
| Date: | 2009-08-10 17:59:56 |
| Message-ID: | dcc563d10908101059u65bed965qce10cec703308ce6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Aug 10, 2009 at 12:58 AM, cjm1010<cjm1010(at)naver(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Hart | 2009-08-10 18:02:06 | Re: PQstatus does not seem to work |
| Previous Message | Vick Khera | 2009-08-10 17:49:02 | Re: Postgres memory question |