| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Rod Taylor <pg(at)rbt(dot)ca> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL Anniversary Proposals -- Important Update |
| Date: | 2006-03-20 14:19:56 |
| Message-ID: | 20060320141955.GQ15742@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
On Sat, Mar 18, 2006 at 12:38:30PM -0500, Rod Taylor wrote:
> One example might be a 'self-aggregating' structure. Start with one
> entry per minute in a table indexed by time. After 2 weeks passes, the
> per-minute data is aggregated and the single entry at the start of the
> day is updated with the aggregate value with the other entries for the
> day being removed. I believe this can cause significant index bloat
> since it results in a few entries per page in the index.
FYI, that's exactly what http://rrs.decibel.org does (yeah, I know,
viewcvs is down... :( )
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guido Barosio | 2006-03-20 17:23:52 | Sony Online Entertainment and PostgreSQL |
| Previous Message | Robert Treat | 2006-03-20 12:15:53 | Re: [HACKERS] PostgreSQL Anniversary Proposals --Important Update |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christian Mair | 2006-03-20 17:38:20 | Re: [Pgbuildfarm-members] guppie: 64MB RAM too small? |
| Previous Message | Martijn van Oosterhout | 2006-03-20 12:17:15 | Re: Question about MemoryContexts and functions that returns sets. |