| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, mfatticcioni(at)mbigroup(dot)it, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: DRBD and Postgres: how to improve the perfomance? |
| Date: | 2007-09-08 18:22:24 |
| Message-ID: | 02B6620CD34BA4D0F4A62C45@imhotep.credativ.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
--On Samstag, September 08, 2007 12:39:37 -0400 Tom Lane
<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> However, it seems like the point here is not so much "can you recover
> your data" as what a commit means. Do you want a commit reported to the
> client to mean the data is safely down to disk in both places, or only
> one?
Yeah, that's what i meant to say. DRBD provides a handful other tweaks
besides changing the sync protocol, i'd start with them first. You can get
back experimenting with the sync protocol if there are still performance
issues then. I don't hesitate changing to B as long as I'm aware that it
changed semantics and I can deal with them.
--
Thanks
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-09-08 21:25:13 | Re: DRBD and Postgres: how to improve the perfomance? |
| Previous Message | Gregory Stark | 2007-09-08 17:32:13 | Re: DRBD and Postgres: how to improve the perfomance? |