From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | "Tomeh, Husam" <htomeh(at)firstam(dot)com> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Partitioning Option? |
Date: | 2005-02-23 19:48:42 |
Message-ID: | 20050223194842.GB20776@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, Feb 23, 2005 at 10:54:50 -0800,
"Tomeh, Husam" <htomeh(at)firstam(dot)com> wrote:
> Thanks Josh, I'll check out the namespace concept.
>
> (I was referring to object partitioning. For instance, if I have a huge
> table with US counties as my partition key, I could create partitions
> within the same table based on the partition key (a US county for
> example). When querying, the engine will access the partition instead of
> the whole table to get the result set. This is provided in Oracle DB EE.
> So, I was wondering whether I can do similar thing in PostgreSQL since
> we're exploring PostgreSQL)
You have to do it by hand and you won't get the full savings.
The idea is to create tables for each partition. Then create a UNION ALL
view of the tables, incorporating the key condition that applies for
each table.
From | Date | Subject | |
---|---|---|---|
Next Message | Bjoern Metzdorf | 2005-02-23 21:10:52 | invalid multibyte character for locale |
Previous Message | Tom Lane | 2005-02-23 19:12:26 | Re: Partitioning Option? |