Re: DETACH PARTITION and FOR EACH ROW triggers on partitioned tables - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: DETACH PARTITION and FOR EACH ROW triggers on partitioned tables
Date
Msg-id 20200421164510.GJ3890@telsasoft.com
Whole thread Raw
In response to Re: DETACH PARTITION and FOR EACH ROW triggers on partitioned tables  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Tue, Apr 21, 2020 at 12:20:38PM -0400, Alvaro Herrera wrote:
> diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
> index 7595e609b5..233905552c 100644
> --- a/doc/src/sgml/ref/alter_table.sgml
> +++ b/doc/src/sgml/ref/alter_table.sgml
> @@ -941,13 +943,14 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
>      <term><literal>DETACH PARTITION</literal> <replaceable class="parameter">partition_name</replaceable></term>
>      <listitem>
>       <para>
>        This form detaches specified partition of the target table.  The detached
>        partition continues to exist as a standalone table, but no longer has any
>        ties to the table from which it was detached.  Any indexes that were
> -      attached to the target table's indexes are detached.
> +      attached to the target table's indexes are detached.  Any triggers that
> +      were created to mirror those in the target table are removed.

Can you say "cloned" here instead of mirror ?
> +      attached to the target table's indexes are detached.  Any triggers that
> +      were created as clones of triggers in the target table are removed.

Also, I see in the surrounding context a missing word? 
This form detaches THE specified partition of the target table.

-- 
Justin



pgsql-hackers by date:

Previous
From: yuzuko
Date:
Subject: Re: Autovacuum on partitioned table (autoanalyze)
Next
From: Robert Haas
Date:
Subject: Re: design for parallel backup