public inbox for [email protected]  

help / color / mirror / Atom feed

From: Simon Riggs <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: [email protected]
Subject: Re: Inheritance and Partitioning
Date: Sun, 09 Oct 2005 20:48:38 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On Sun, 2005-10-09 at 10:56 -0300, Alvaro Herrera wrote:
> Simon Riggs wrote:
> > I'm currently doing the docs for CE & Partitioning.
> > 
> > The ddl.sgml chapter had a section on Inheritance. I'm expanding that
> > section and splitting it into two:
> > 
> > INHERITANCE & PARTITIONING
> >    1. Table Partitioning
> >       Existing chapter, but with more detail of a general nature that
> > will be important information when we discuss...
> > 
> >    2. Basic Partitioning using Constraint Exclusion
> >       How to enhance inheritance with constraints to allow CE. How that
> > works to provide basic partitioning, with examples and long list of
> > caveats.
> 
> Hmm, sorry, I missed most of the discussion on CE -- is it used only
> in inheritance?  

Regrettably at this time. I couldn't find a clear point to put the code
that would allow it to work cleanly for the UNION ALL case, at least in
the time available.

> Maybe you should add a separate section on
> partitioning, referring to the inheritance section where appropiate.
> But they are clearly not the same feature.
> 
> Also, it will be more clearly separated as we add more partitioning
> related features, right?

OK. I'll keep the same flow, just promote both up a level.

So there'll be two <sect1>s for each concept.

Best Regards, Simon Riggs

view thread (3+ messages)

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: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Inheritance and Partitioning
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox