| From: | Gerald Gutierrez <gml1(at)coldresist(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Table partitioning? |
| Date: | 2001-06-10 08:22:06 |
| Message-ID: | 5.1.0.14.0.20010610012200.02b9b3f0@mail.rchmd1.bc.wave.home.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I was browsing some database mailing lists and found this message available
at:
----------
(http://www.phpbuilder.com/forum/read.php3?num=2&id=139678&thread=139671)
I don't know MSSQL, but if it tries to compete with Oracle, it should have
this funcitonality (which oracle does):
divide tables into smaller tables that are searched on queries based on a
set field/rule.
An example of this would be: given the first character of a text column,
insert the row into the table partition that has other rows with the same
letter. When a query is done where mycol = 'axxs'; the first thing Oracle
does is decide which table partition to use and then does the rest of the
where statement.
You should be able to design a database application without ever caring how
many rows will be in each table...as I said, dealing with that is a DBA issue.
----------
It seems that, depending on how data is actually stored on disk and
accessed, this method of partitioning a table internally in the database
could be a benefit. Has anyone investigated this for PostgreSQL?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2001-06-10 09:32:11 | Re: PGDG? |
| Previous Message | Gerald Gutierrez | 2001-06-10 04:40:50 | Table partitioning? |