| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com> |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Fujii Masao" <masao(dot)fujii(at)gmail(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Synchronization levels in SR |
| Date: | 2010-05-26 17:10:22 |
| Message-ID: | 4BFD0FAE0200002500031B0A@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> One way to do that would be to refrain from flushing the commit
> record to disk on the master until the standby has acknowledged
> it.
I'm not clear on the benefit of doing that, versus flushing the
commit record and then waiting for responses. Either way some
databases will commit before others -- what is the benefit of having
the master lag?
> Adding a synchronous standby should require some action in the
> master, since it affects the behavior on master.
+1
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-05-26 17:17:31 | Re: Exposing the Xact commit order to the user |
| Previous Message | Heikki Linnakangas | 2010-05-26 16:55:30 | Re: Synchronization levels in SR |