| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | tfinneid(at)student(dot)matnat(dot)uio(dot)no |
| Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Gregory Stark" <stark(at)enterprisedb(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: select count() out of memory |
| Date: | 2007-10-25 16:18:36 |
| Message-ID: | 17330.1193329116@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
tfinneid(at)student(dot)matnat(dot)uio(dot)no writes:
>> In that case, why use partitions at all? They are simple independent
>> tables.
> For two reasons,
> - the data logically belongs together.
> - because its more practical to create tables as childs of a parent table
> than as independent tables.
> - changes to the table is applied to all partitions, and prohibits
> tables with different dd.
> - performing the create operation does not require the source code to
> contain the ddl of the parent table.
In other words, you really should have only one table; they aren't
independent. What you need to do is dial down your ideas of how many
partitions are reasonable to have.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Reg Me Please | 2007-10-25 16:24:56 | Re: subversion support? |
| Previous Message | Alvaro Herrera | 2007-10-25 16:16:31 | Re: select count() out of memory |