Re: pg_xlog_replay_resume() considered armed and dangerous - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: pg_xlog_replay_resume() considered armed and dangerous
Date
Msg-id 55073E43.6040901@BlueTreble.com
Whole thread Raw
In response to pg_xlog_replay_resume() considered armed and dangerous  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On 3/12/15 10:08 AM, Andres Freund wrote:
> I think this, at the very least, needs a big caveat in the documentation
> of the resume function. But a different API would probably be
> better. I'd actually argue that for now pg_xlog_replay_resume() should
> refuse to work if paused due to a recovery target. Promotion should be
> done via the normal promotion methods.

+1. "replay resume" certainly doesn't make me think "promote".
-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Additional role attributes && superuser review
Next
From: Tom Lane
Date:
Subject: Re: Additional role attributes && superuser review