Attached is a doc patch based on a suggestion by Rural Hunter to
address something he found confusing while setting up partitioning.
Original thread is here:
http://archives.postgresql.org/pgsql-admin/2012-03/msg00066.php
-Kevin
*** a/doc/src/sgml/ddl.sgml
--- b/doc/src/sgml/ddl.sgml
***************
*** 2411,2416 **** VALUES ('New York', NULL, NULL, 'NY');
--- 2411,2420 ----
constraints on this table, unless you intend them to
be applied equally to all partitions. There is no point
in defining any indexes or unique constraints on it, either.
+ Because triggers on this table will not be fired for operations
+ on the related partitions, there is usually no reason to create
+ triggers on it other than the optional trigger described below
+ to redirect operations to the appropriate partitions.
</para>
</listitem>
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
