From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, NikhilS <nikkhils(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Auto creation of Partitions |
Date: | 2007-03-07 07:49:53 |
Message-ID: | 45EE6EA1.7010607@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
>
>>
>> Maybe. The most obvious use for automatic partitioning that I can
>> think of would be based in the value of a timestamptz field rather
>> than any PK. Of course I tend to work more in the OLTP field than in
>> DW type apps, where other considerations might apply.
>
> I second that - partitioning on some kind of timestamp field is a
> common usecase here too ...
Partitioning period needs to work. It doesn't matter what the user
chooses as their partition key. Timestamp is an obvious
choice but there are others such as serial where you just partition
every million rows (for example) to keep things manageable.
Joshua D. Drake
>
>
> Stefan
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2007-03-07 08:18:36 | Re: PostgreSQL - 'SKYLINE OF' clause added! |
Previous Message | Hannu Krosing | 2007-03-07 07:22:04 | Re: Bug: Buffer cache is not scan resistant |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2007-03-07 09:01:21 | Re: Auto creation of Partitions |
Previous Message | Stefan Kaltenbrunner | 2007-03-07 07:20:19 | Re: Auto creation of Partitions |