From: | "Josh Harrison" <joshques(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: update problem in partitioned tables |
Date: | 2007-09-12 17:05:31 |
Message-ID: | 8d89ea1d0709121005i4bd0e4bex559aa23646af453a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks. Check this website that talk abt the approach that I had mentioned
http://blogs.ittoolbox.com//oracle/guide/archives/comparing-partitioned-tables-in-oracle-and-enterprisedbpostgresql-13261
I also tried your method (triggers on the child table) and it gives the same
error too.
Josh
On 9/12/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Josh Harrison" <joshques(at)gmail(dot)com> writes:
> > Now I create this function to redirect the inserts and updates on the
> > master table.
>
> Uh ... there never will be any updates in the master table, since it
> hasn't got any entries.
>
> What you'd need is an insert trigger on the master and update triggers
> on each child table. I think the logic of this trigger is wrong for
> the update case anyway.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | finecur | 2007-09-12 17:05:43 | Re: constrains on two tables |
Previous Message | Alvaro Herrera | 2007-09-12 17:01:16 | Re: problems with large table |