Re: Re: [COMMITTERS] pgsql: Send new protocol keepalive messages to standby servers.
Magnus Hagander <magnus@hagander.net>
From: Magnus Hagander <magnus@hagander.net>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, Fujii Masao <masao.fujii@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-08-09T16:13:42Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Send new protocol keepalive messages to standby servers.
- 64233902d22b 9.2.0 cited
On Thu, Aug 9, 2012 at 6:11 PM, Simon Riggs <simon@2ndquadrant.com> wrote: > On 5 June 2012 23:55, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Simon Riggs <simon@2ndQuadrant.com> writes: >>> Can't we have a trial branch where quarantined patches can be placed >>> on trial for inclusion in main release? >> >> [ shrug... ] You're welcome to publish a personal repo somewhere with >> such things. But even if we did that in the master repo, it would have >> approximately nothing to do with released versions. You might as well >> just figure on submitting the patch into 9.3. > > In an effort to resolve the PG9.2 open item on keepalives, I have > > * Ensured we have full and correct info about replication messages > available for analysis > > * Turned off keepalives by default, keeping all code. It can be turned > on again by someone that knows how. > > I will later do this > > * Publish functions that can turn on keepalives and analyse info from > them, making them available as an Extension for 9.2 > > Later meaning not during the next two weeks, but by Sep 15. > > That's about the simplest way of resolving it I can think of, so I > hope that's fine for y'all. Ah, wrong order of messages.Here's the explanation, you can disregard my last one. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/