From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Josh Berkus <josh@agliodbs.com>
To: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
To: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Declarative partitioning
Date: Fri, 21 Aug 2015 22:34:21 -0500
Message-ID: <55D7EDBD.50008@BlueTreble.com> (raw)
In-Reply-To: <55D36BFA.7080004@agliodbs.com>
References: <55D3093C.5010800@lab.ntt.co.jp>
<WM!d7710f5363855cdb19d569b89c9c5e583742def1a8442d29ccee7f2591bfe40e9b26d6d9500448c2078cac09dedcf224!@asav-3.01.com>
<55D36BFA.7080004@agliodbs.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 8/18/15 12:31 PM, Josh Berkus wrote:
> Also this would be useful for range
> partitions:
>
> CREATE PARTITION ON parent_table USING ( start_value );
>
> ... where start_value is the start range of the new partition. Again,
> easier for users to get correct.
Instead of that, I think it would be more foolproof to do
CREATE PARTITION ON parent_table FOR ( value1, ... );
instead of trusting the user to get the exact start value correct.
Though... I guess there could be value in allowing an exact start value
but throwing an error if it doesn't sit exactly on a boundary. Might
make it less likely to accidentally create the wrong partition.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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: Jim.Nasby@BlueTreble.com, josh@agliodbs.com, Langote_Amit_f8@lab.ntt.co.jp
Subject: Re: Declarative partitioning
In-Reply-To: <55D7EDBD.50008@BlueTreble.com>
* 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