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 16:26:15 |
Message-ID: | 47417.134.32.140.234.1193329575.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:
>> > 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.
>
> You can use CREATE TABLE LIKE, which copies the definition but does not
> set the inheritance.
I know, but point 1 of reason 2 was why I decided against it. I was
discussing the different options with myself when I was trying to decide,
and I decided on the partitions. So unless there will be a problem with
the real operations, I cant se any reason to change.
regards
thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Jones | 2007-10-25 16:27:09 | Re: select count() out of memory |
Previous Message | Reg Me Please | 2007-10-25 16:24:56 | Re: subversion support? |