From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | dbatoCloud Solution <dbatocloud17(at)gmail(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Partitioning existing table issue - Help needed! |
Date: | 2021-02-04 14:10:40 |
Message-ID: | CABUevExYmH6pHajagD5DD8Rm9cHXiWP+YtRMcOSbrQTBej1NkQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thu, Feb 4, 2021 at 2:47 PM dbatoCloud Solution
<dbatocloud17(at)gmail(dot)com> wrote:
>
> Dear All,
>
> I am partitioning the large table using declarative partitioning method in PostgreSQL 10.13.
>
>
>
> The below steps which I am using are :
>
>
>
> created parent table
> create sub-partitioned table
> created index for each partition
> created function
> creating trigger but end with below error:-
>
> SQL Error [42809]: ERROR: "contact_transaction_history_parent_part_bkp_am" is a partitioned table
>
> Detail: Partitioned tables cannot have ROW triggers.
>
>
>
> Please let me know what is the issue with this?
The ability to add row triggers on partitioned tables was added in
PostgreSQL 11, see the release notes at
https://www.postgresql.org/docs/11/release-11.html.
In v10 you have to create the triggers individually for each partition.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Vasily Alexeev | 2021-02-04 16:32:25 | Postgres stuck on recovery after running out of disk space |
Previous Message | dbatoCloud Solution | 2021-02-04 13:47:48 | Partitioning existing table issue - Help needed! |