| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Mark Kirkwood" <markir(at)paradise(dot)net(dot)nz>, "Andrew Sullivan" <ajs(at)crankycanuck(dot)ca> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Introducing an advanced Frequent Update Optimization |
| Date: | 2006-11-09 18:05:22 |
| Message-ID: | 1163095523.3634.498.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2006-11-07 at 15:00 +1300, Mark Kirkwood wrote:
> Simon Riggs wrote:
> > EnterpriseDB has been running a research project to improve the
> > performance of heavily updated tables. We have a number of approaches
> > prototyped and we'd like to discuss the best of these now on -hackers
> > for community input and patch submission to PostgreSQL core.
> >
>
> Excellent! It would certainly be good for use cases like:
>
> - session data from web (or similar) applications
> - real time summary tables maintained by triggers
>
> to "just work", as (certainly in the case of the first one) quite a few
> folks have been bitten by exactly the issue you describe.
...and of course it would be good if LISTEN/NOTIFY were able to use this
concept also, to help Slony along also.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2006-11-09 21:21:21 | Re: Frequent Update Project: Design Overview of HOT Updates |
| Previous Message | Simon Riggs | 2006-11-09 17:57:17 | Re: Frequent Update Project: Design Overview of HOTUpdates |