From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: What needs to be done for real Partitioning?
Date: Sat, 19 Mar 2005 15:49:28 -0500
Message-ID: <18168.1111265368@sss.pgh.pa.us> (raw)
In-Reply-To: <200503191202.38089.josh@agliodbs.com>
References: <200503191202.38089.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
> -- CREATE TABLE ... WITH PARTITION ON {expression}
I'd rather see the partition control stuff as ALTER TABLE commands,
not decoration on CREATE TABLE. See the WITH OIDS business we just went
through: adding nonstandard decoration to a standard command isn't good.
> -- INSERT INTO should automatically create new partitions where necessary
> -- DELETE FROM should automatically drop empty partitions
I am not sure I agree with either of those, and the reason is that they
would turn low-lock operations into high-lock operations. DELETE FROM
would be particularly bad. Furthermore, who wants to implement DROP
PARTITION as a DELETE FROM? ISTM the whole point of partitioning is to
be able to load and unload whole partitions quickly, and having to
DELETE all the rows in a partition isn't my idea of quick.
> -- setting of WITH PARTITION ON {expression} TABLESPACE should automatically
> create a new tablespace for each new partition and its indexes.
This is a bad idea. Where are you going to create these automatic
tablespaces? What will they be named? Won't this require superuser
privileges? And what's the point anyway?
> -- It should be possible to create new, empty partitions via a CREATE TABLE
> PARTITION OF {table} ON {value} expression.
Huh? ISTM this confuses establishment of a table's partition rule with
the act of pre-creating empty partitions for not-yet-used ranges of
partition keys. Or are you trying to suggest that a table could be
partitioned more than one way at a time? If so, how?
regards, tom lane
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com
Subject: Re: What needs to be done for real Partitioning?
In-Reply-To: <18168.1111265368@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