pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Corey Huinker <corey.huinker@gmail.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Documentation improvements for partitioning
Date: Wed, 15 Feb 2017 12:11:18 -0500
Message-ID: <16559.1487178678@sss.pgh.pa.us> (raw)
In-Reply-To: <20170215163411.7ozquqahgf64lvui@alvherre.pgsql>
References: <20170215163411.7ozquqahgf64lvui@alvherre.pgsql>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Robert Haas wrote:
>> True.  I think the question here is: do we want to view the dependency
>> between a partitioned table and a partition of that table as
>> DEPENDENCY_NORMAL or as DEPENDENCY_AUTO?  With table inheritance, it's
>> always been "normal" and I'm not sure there's any good reason for
>> partitioning to make the opposite decision.

> I think new-style partitioning is supposed to consider each partition as
> an implementation detail of the table; the fact that you can manipulate
> partitions separately does not really mean that they are their own
> independent object.  You don't stop to think "do I really want to drop
> the TOAST table attached to this main table?" and attach a CASCADE
> clause if so.  You just drop the main table, and the toast one is
> dropped automatically.  I think new-style partitions should behave
> equivalently.

I agree with Alvaro's position.  If you need CASCADE to get rid of the
individual partitions, that's going to be a serious usability fail.

			regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (71+ messages)  latest in thread

Message-ID: <16559.1487178678@sss.pgh.pa.us>
Permalink:  ../16559.1487178678@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/16559.1487178678@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, robertmhaas@gmail.com, jd@commandprompt.com, simon@2ndquadrant.com, Langote_Amit_f8@lab.ntt.co.jp, corey.huinker@gmail.com
  Subject: Re: Documentation improvements for partitioning
  In-Reply-To: <16559.1487178678@sss.pgh.pa.us>

* 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