From: Michael Paquier <michael@paquier.xyz>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: TRUNCATE tables referenced by FKs on partitioned tables
Date: Thu, 12 Jul 2018 11:53:08 +0900
Message-ID: <20180712025308.GA7352@paquier.xyz> (raw)
In-Reply-To: <20180711225916.domrlbkmukhrg6jg@alvherre.pgsql>
References: <20180711071647.GC14301@paquier.xyz>
<20180711225916.domrlbkmukhrg6jg@alvherre.pgsql>
On Wed, Jul 11, 2018 at 06:59:16PM -0400, Alvaro Herrera wrote:
> Anyway, this patch seems to fix it, and adds what I think is appropriate
> test coverage.
This looks good to me. I am noticing that the documentation of TRUNCATE
does not mention that when running the command on a partitioned table
then it automatically gets to the children even if CASCADE is not used
and each child partition is not listed.
What is the filler column added in truncpart used for?
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
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-hackers@postgresql.org
Cc: michael@paquier.xyz, alvherre@2ndquadrant.com
Subject: Re: TRUNCATE tables referenced by FKs on partitioned tables
In-Reply-To: <20180712025308.GA7352@paquier.xyz>
* 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