| From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: Time to start the PR machine |
| Date: | 2005-09-30 20:13:45 |
| Message-ID: | 1128111226.5788.39.camel@camel |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On Fri, 2005-09-30 at 13:31, Joshua D. Drake wrote:
> Shared Row Locking: PostgreSQL's "better than row-level
> locking" has been improved further through the addition of
> shared row locks for foreign keys. Shared locks will improve
> insert and update performance on some OLTP applications
> ^^^^
>
> The word "some" sounds like it is a minority of OLTP applications.
> In general any moderately used OLTP app will benifit from this yes?
>
> many, most, or just say performance on OLTP applications.
>
well, it will really only help on those systems that were stressing out
our current design (and thats really hardware dependent too) so maybe
"busy", "heavy","high load" or just "on OLTP applications".
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2005-09-30 20:29:35 | Re: XA |
| Previous Message | Robert Treat | 2005-09-30 19:27:38 | PR: release text updated |