Re: Partitioning existing table issue - Help needed!

Thanks Magnus,

I was able to create trigger for each partition now successfully.

Now I tried to insert records from the old tableto newly created partition
table but I am receiving the below error.
Comand # insert into core.contact_transaction_history_Parent_PART_BKP_AM
select * from core.contact_transaction_history;

*SQL Error [54001]: ERROR: stack depth limit exceeded Hint: Increase the
configuration parameter "max_stack_depth" (currently 6144kB), after
ensuring the platform's stack depth limit is adequate.*
Where: SQL statement "INSERT INTO
core.contact_transaction_history_P_PART_BKP_Y2020_AM VALUES (NEW.*)"
PL/pgSQL function core.contact_transaction_history_parent_part_bkp_am_()
line 14 at SQL statement
SQL statement "INSERT INTO
core.contact_transaction_history_P_PART_BKP_Y2020_AM VALUES (NEW.*)"
PL/pgSQL function core.contact_transaction_history_parent_part_bkp_am_()
line 14 at SQL statement
SQL statement "INSERT INTO
core.contact_transaction_history_P_PART_BKP_Y2020_AM VALUES (NEW.*)"
PL/pgSQL function core.contact_transaction_history_parent_part_bkp_am_()
line 14 at SQL statement
SQL statement "INSERT INTO
core.contact_transaction_history_P_PART_BKP_Y2020_AM VALUES (NEW.*)"
PL/pgSQL function core.contact_transaction_history_parent_part_bkp_am_()
line 14 at SQL statement
SQL statement "INSERT INTO
core.contact_transaction_history_P_PART_BKP_Y2020_AM VALUES (NEW.*)"
PL/pgSQL function core.contact_transaction_history_parent_part_bkp_am_()
line 14 at SQL statement
SQL statement "INSERT INTO
core.contact_transaction_history_P_PART_BKP_Y2020_AM VALUES (NEW.*)"
PL/pgSQL function core.contact_transaction_history_parent_part_bkp_am_()
line 14 at SQL statement

Thanks & Best Wishes,

Ashok

---------------------------------------------------------------------------------------------------------------------

Ashokkumar Mani *(OCP12c/11g/10g/9i, AWS SAA, M103)*

*Dubai** , UAE* *| BLR , INDIA*

M: *+971 54 723 0075 *| *+91 90086 70302 | *WApp :* +91 81975 99922*

W: https://dbatocloudsolution.blogspot.in/
<http://dbatocloudsolution.blogspot.in/> | E: dbatocloud17(at)gmail(dot)com

On Thu, Feb 4, 2021 at 7:40 PM Magnus Hagander <magnus(at)hagander(dot)net> wrote:

> 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/
>