Rocco Altier wrote:
> > From: pgsql-hackers-owner@postgresql.org
> > [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Hannu Krosing
> >
> > Ühel kenal päeval, T, 2006-08-29 kell 22:12, kirjutas Joshua D. Drake:
> > > >> Auto creations of partitions
> > >
> > > This would be something like:
> > >
> > > create table foo () partition by ...
> >
> > from the referenced MySQL manual entry
> >
> > CREATE TABLE members (
> > ...
> > joined DATE NOT NULL
> > )
> > PARTITION BY KEY(joined)
> > PARTITIONS 6;
> >
> > Do you have any idea how this should work ?
> >
> > What date range should go into which partition ?
>
> Since we don't have any knowledge about the date ranges in question,
> and the fact that they could change over time, I think the only stable
> way to handle this scenario would be to use a hash function which had
> 6 buckets (something like 'date % 6' could work).
IMHO we shouldn't be giving too many partitioning options until we solve
the important problems it brings with it, like FKs or unique constraints
not working across the hierarchy.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
