From: Thomas Kellerer <shammat@gmx.net>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Partitioning existing table issue - Help needed!
Date: Fri, 5 Feb 2021 15:50:35 +0100
Message-ID: <156bd5b9-d9aa-cfc2-d584-a8dd82acaf66@gmx.net> (raw)
In-Reply-To: <CAEz7P_v93GF4_irRugWvz7SrCNVHFEihEbuotaDJGu=WGyWbpQ@mail.gmail.com>
References: <CAEz7P_v93GF4_irRugWvz7SrCNVHFEihEbuotaDJGu=WGyWbpQ@mail.gmail.com>
dbatoCloud Solution schrieb am 04.02.2021 um 14:47:
> Dear All,
>
> I am partitioning the large table using declarative partitioning method in PostgreSQL 10.13.
>
> 1. created parent table
> 2. create sub-partitioned table
> 3. created index for each partition
> 4. created function
> 5. 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.
What do you need the trigger for?
And what does the trigger do?
If you insert into the parent table, Postgres will automatically store
the row in the appropriate partition.
Apart from the need to upgrade because row triggers on a partitioned table require Postgres 11,
you might want to consider upgrading to at least Postgres 12 anyway, as there were
substantial partitioning improvements in 11 and 12 (performance and usability wise)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: shammat@gmx.net, pgsql-admin@lists.postgresql.org
Subject: Re: Partitioning existing table issue - Help needed!
In-Reply-To: <156bd5b9-d9aa-cfc2-d584-a8dd82acaf66@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox