While working on something else, I noticed $SUBJECT: we do not currently allow row-level triggers on partitioned tables to have transition tables like this:
create table parted_trig (a int) partition by list (a); CREATE TABLE create function trigger_nothing() returns trigger language plpgsql as $$ begin end; $$; CREATE FUNCTION create trigger failed after update on parted_trig referencing old table as old_table for each row execute procedure trigger_nothing(); ERROR: "parted_trig" is a partitioned table DETAIL: Triggers on partitioned tables cannot have transition tables. but the DETAIL message is confusing, because statement-level triggers on partitioned tables *can* have transition tables. We do not currently allow row-level triggers on partitions to have transition tables either, and the error message for that is “ROW triggers with transition tables are not supported on partitions.”. How about changing the DETAIL message to something similar to this like “ROW triggers with transition tables are not supported on partitioned tables.”, to avoid confusion? Patch attached. Will add this to the upcoming CF. Best regards, Etsuro Fujita
fix-trigger-error-message.patch
Description: Binary data
