From: | Chetan Suttraway <chetan(dot)suttraway(at)enterprisedb(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, u235sentinel(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Auto-extending table partitions? |
Date: | 2010-01-07 14:31:16 |
Message-ID: | d26e86811001070631o7848a658gd9e717920121720@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Adding on to this use case:
what do we do when we reach end of year?
Probably auto-archive as per weekly, monthly , quarterly or yearly tables?
On Thu, Jan 7, 2010 at 1:14 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 1/6/10 9:13 AM, Robert Haas wrote:
> > On Wed, Jan 6, 2010 at 12:06 PM, David Fetter <david(at)fetter(dot)org> wrote:
> >> On Tue, Jan 05, 2010 at 08:50:25PM -0700, u235sentinel wrote:
> >>> Robert Haas wrote:
> >>>> Getting full?
> >>>>
> >>>> ...Robert
> >>>>
> >>> Ok. Bad analogy. We have the tables setup to write data according
> >>> to the month it was loaded. We have a December table, a January
> >>> table and so on. Basically following the examples given on the 8.4
> >>> web site.
>
> FWIW, our roadmap is to add a 2nd type or partitioning which would be on
> the sub-table level and much more automated for that reason.
>
> --Josh Berkus
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
--
Chetan Sutrave
http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2010-01-07 14:35:52 | Re: pg_migrator issues |
Previous Message | Stefan Kaltenbrunner | 2010-01-07 14:19:44 | Re: unresolved bugs |