Re: Sync Rep: First Thoughts on Code - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Sync Rep: First Thoughts on Code
Date
Msg-id 1229107160.12977.21.camel@dell.linuxdev.us.dell.com
Whole thread Raw
In response to Re: Sync Rep: First Thoughts on Code  (Aidan Van Dyk <aidan@highrise.ca>)
Responses Re: Sync Rep: First Thoughts on Code  (Aidan Van Dyk <aidan@highrise.ca>)
List pgsql-hackers
On Fri, 2008-12-12 at 08:57 -0500, Aidan Van Dyk wrote:
> > For (2) we need a full interlock. Given that we don't currently support
> > multiple streamed standby servers, it seems not much point in
> > implementing the interlock (2) would require. Should we leave that part
> > for 8.5, or do it now?
> 
> Ugh... If all sync-rep is gong to give is "if it's working, the commit
> made it the slaves, but it might not be working [anymore|yet], but you
> (the app using pg) have no way of knowing...", that sort of defeats the
> point ;-)

http://archives.postgresql.org/pgsql-hackers/2008-12/msg00865.php

Fujii Masao offers to provide a SQL function that will tell you
definitively whether you are in full sync rep, or some degraded mode. I
assume that there will also be server log messages to identify whether
you ever left sync rep mode.

Regards,Jeff Davis



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: benchmarking the query planner
Next
From: Tom Lane
Date:
Subject: Re: benchmarking the query planner