ECTED]
Sent: Thursday, November 16, 2006 12:39 PM
To: Mark Steben
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Question on partitioning
On Wed, 2006-11-15 at 15:13 -0500, Mark Steben wrote:
> Regarding partitioning - I set up a testing table - parent table and 4
> partitioning childr
On Wed, 2006-11-15 at 15:13 -0500, Mark Steben wrote:
> Regarding partitioning – I set up a testing table – parent table and 4
> partitioning children’s tables inheriting the
>
> Attributes of the parent. I inserted 1800 rows in all – 450 equitably
> in each partition. The CHECK constraints work
Hi, the new guy is back with another
question.
Regarding partitioning – I set up a
testing table – parent table and 4 partitioning children’s tables
inheriting the
Attributes of the parent. I inserted
1800 rows in all – 450 equitably in each partition. The CHECK constraints
work great
> > My question is this: How would I handle a query that queries
> > On another Non-partitioned column, say, ENTRY_DATE? Could I design an index
> > On the master table that would reference ENTRY-DATE across partitions or
> > will
> > I need to build indexes and queries on each partition?
Inde
> Thanks to all who responded to my question on querying on cluster index
> names.
> I have another question. We are considering partitioning 2 or 3 of our
> larger tables.
> Each has 12 million or more rows. We want to partition on customer_id and
> build
> Primary key indexes on each of the chi
Thanks to all who responded to my question
on querying on cluster index names.
I have another question. We are considering
partitioning 2 or 3 of our larger tables.
Each has 12 million or more rows. We
want to partition on customer_id and
build
Primary key indexes on each of the
chi
