| From: | pgsql(at)mohawksoft(dot)com |
|---|---|
| To: | "Steve Atkins" <steve(at)blighty(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Accelerating aggregates |
| Date: | 2004-06-11 15:16:19 |
| Message-ID: | 16942.24.91.171.78.1086966979.squirrel@mail.mohawksoft.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
[snip]
I've been harping on this problem myself the last couple days.
A summary table with frequent vacuums is your best bet for the existing
versions of PostgreSQL. It is, IMHO, suboptimal, but a workable solution
depending on the expected database load.
Right now I am exploring the possibility of writing a set of msession
functions for PostgreSQL. The msession project is a high speed high volume
session manager for PHP based websites.
Using PostgreSQL's recent ability to return sets of rows from functions,
it should be possible to create a set of msession functionality in
PostgreSQL that allows really FAST and really temporary variables that,
while syntactically different, behave much like simple tables.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Atkins | 2004-06-11 15:26:05 | Re: Accelerating aggregates |
| Previous Message | Christopher Kings-Lynne | 2004-06-11 12:51:39 | Re: [COMMITTERS] pgsql-server: Clean up generation of default |