Re: max_standby_delay considered harmful

Simon Riggs <simon@2ndquadrant.com>

From: Simon Riggs <simon@2ndQuadrant.com>
To: Florian Pflug <fgp@phlo.org>
Cc: Dimitri Fontaine <dfontaine@hi-media.com>, Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org, Bruce Momjian <bruce@momjian.us>, Greg Smith <greg@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Josh Berkus <josh@agliodbs.com>
Date: 2010-05-09T19:04:02Z
Lists: pgsql-hackers
On Sun, 2010-05-09 at 16:10 +0200, Florian Pflug wrote:

> Adding pause/resume seems to introduce some non-trivial locking
> problems, though. How would you handle a pause request if the recovery
> process currently held a lock?

(We are only talking about AccessExclusiveLocks here. No LWlocks are
held across WAL records during replay)

Just pause. There are no technical problem there.

Perhaps a danger of unforeseen consequences, though doing that might
also be desirable, who can say?

-- 
 Simon Riggs           www.2ndQuadrant.com