From: | Erik Jones <erik(at)myemma(dot)com> |
---|---|
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:27:09 |
Message-ID: | DA1B8EEB-69D0-4636-8EA6-B48777BF6F04@myemma.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Oct 25, 2007, at 11:16 AM, Alvaro Herrera wrote:
> 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.
That won't propogate changes made later.
Erik Jones
Software Developer | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
From | Date | Subject | |
---|---|---|---|
Next Message | tfinneid | 2007-10-25 16:34:39 | Re: select count() out of memory |
Previous Message | tfinneid | 2007-10-25 16:26:15 | Re: select count() out of memory |