| From: | Chris <dmagick(at)gmail(dot)com> |
|---|---|
| To: | Tore Lukashaugen <tore(at)lukashaugen(dot)freeserve(dot)co(dot)uk> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Partitioning in postgres - basic question |
| Date: | 2007-10-05 05:19:23 |
| Message-ID: | 4705C95B.2040603@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Tore Lukashaugen wrote:
> Hi,
>
> I am new to postgres having worked with Oracle in the past. I am interested
> in understanding Postgres's table partition functionality better.
> Specifically, I have a third party application running against my postgres
> database, but the database is becoming rather large to maintain. I am
> thinking about partitioning the biggest table.
>
> Would I be able to set-up partitioning on this table with it being seemless
> to the third party app (assuming that it performs pretty standard DML
> statements against the table in question)?
http://www.postgresql.org/docs/8.2/static/ddl-partitioning.html#DDL-PARTITIONING-IMPLEMENTATION
The examples use rules but some on the list have said triggers work
better if you have a lot of partitions.
--
Postgresql & php tutorials
http://www.designmagick.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Benjamin Arai | 2007-10-05 07:50:17 | Slow TSearch2 performance for table with 1 million documents. |
| Previous Message | Alvaro Herrera | 2007-10-04 23:43:31 | Re: Query taking too long. Problem reading explain output. |