Re: checkpoints are duplicated even while the system is idle - Mailing list pgsql-hackers

From Tom Lane
Subject Re: checkpoints are duplicated even while the system is idle
Date
Msg-id 4671.1317923781@sss.pgh.pa.us
Whole thread Raw
In response to Re: checkpoints are duplicated even while the system is idle  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: checkpoints are duplicated even while the system is idle  (Simon Riggs <simon@2ndQuadrant.com>)
Re: checkpoints are duplicated even while the system is idle  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes:
> Do we want this backpatched? If so, suggest just 9.1 and 9.0?

-1 for backpatching; it's more an improvement than a bug fix.

In any case, I think we still need to respond to the point Kevin made
about how to tell an idle master from broken replication.  Right now,
you will get at least a few bytes of data every checkpoint_timeout
seconds.  If we change this, you won't.

I'm inclined to think that the way to deal with that is not to force out
useless WAL data, but to add some sort of explicit "I'm alive" heartbeat
signal to the walsender/walreceiver protocol.  The hard part of that is
to figure out how to expose it where you can see it on the slave side
--- or do we have a status view that could handle that?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [REVIEW] Patch for cursor calling with named parameters
Next
From: Tom Lane
Date:
Subject: Re: checkpoints are duplicated even while the system is idle