On Fri, Oct 01, 2010 at 07:48:25PM +0900, Fujii Masao wrote: > I proposed to implement the "return-immediately" at first because it > doesn't require standby registration. But if many people think that > the "wait-forever" is the core rather than the "return-immediately", > I'll follow them. We can implement the "return-immediately" after > that.
In my experience, most people who want "synchronous" behavior are willing to put up with "wait forever," especially when asynchronous behavior is already available. In short, +1 for "push 'wait forever' soonest." Anybody who's got a Secret Base, Hidden in a Hollowed-Out Mountain, Making Grand Plans While Stroking a Long-Haired Cat[1], should please to update their public repository, or create a public repository if it doesn't already exist, and in either case keep it current. Cheers, David [1] While the Hollowed-Out Mountain trick worked back in the 60s, it's gotten a little trite. The cool kids are keeping things pretty public these days when they plan to go public. -- David Fetter <da...@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
