| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>, Gaetano Mendola <mendola(at)bigfoot(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: devx article |
| Date: | 2004-08-21 03:08:45 |
| Message-ID: | 17583.1093057725@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
>> "MySQL does, however, support the advanced feature of data partitioning
>> within a database. PostgreSQL does not."
> Well there is table partitioning and then there is tablespaces.
> PostgreSQL 8 supports table spaces but not table partitioning.
Note that it's possible to roll-your-own table partitioning in PG, using
either views of table unions or inheritance. It's not going to be as
simple to use as a hard-wired implementation, but on the other hand you
might have more flexibility to tune it to your needs. You can find
reports in the archives from people doing exactly this sort of thing.
The above quote is undoubtedly copied straight from some MySQL marketing
materials, rather than being the result of any serious investigation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-08-21 03:21:32 | pg_hba.conf and Solaris |
| Previous Message | Tom Lane | 2004-08-21 00:35:22 | Re: postgres uptime |