| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Keith <keith(at)keithf4(dot)com> |
| Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Read performance on Large Table |
| Date: | 2015-05-21 16:01:31 |
| Message-ID: | DA2568CB-CFAE-4530-9486-88AA4E3D9179@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On May 21, 2015, at 9:45 AM, Keith <keith(at)keithf4(dot)com> wrote:
>
> If you're just going to do basic time series partitioning, I've written a tool that manages most of it for you. Also does retention management as well and can dump out the old partitions automatically.
Yep, make some partitions ahead of time, plus cron to periodically run in order to stay ahead, is an alternative approach.
> I'm in the process of getting v2.0.0 out that has a lot of new work done, but will only be compatible with Postgres 9.4 (since it uses background workers to have scheduling built in). So if you want to wait, I should have that out soon.
I wouldn’t mind that—I did it the way I did partly because I wanted it all self-contained in PG without external (cron or launchd or…) configuration dependencies.
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | danny | 2015-05-21 16:18:36 | PSQL |
| Previous Message | Gilberto Castillo | 2015-05-21 16:00:58 | Re: Read performance on Large Table |