| From: | tfinneid(at)student(dot)matnat(dot)uio(dot)no |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
| Cc: | tfinneid(at)student(dot)matnat(dot)uio(dot)no, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Gregory Stark" <stark(at)enterprisedb(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: select count() out of memory |
| Date: | 2007-10-25 15:56:21 |
| Message-ID: | 46227.134.32.140.234.1193327781.squirrel@webmail.uio.no |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> tfinneid(at)student(dot)matnat(dot)uio(dot)no wrote:
>> Thats good enough for me, thats exactly what I want.
>
> 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.
regards
thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tfinneid | 2007-10-25 15:58:16 | Re: select count() out of memory |
| Previous Message | tfinneid | 2007-10-25 15:50:45 | Re: select count() out of memory |