Re: pg_xlog_replay_resume() considered armed and dangerous

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_xlog_replay_resume() considered armed and dangerous
Date: 2015-03-16 20:34:11
Message-ID: 55073E43.6040901@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2015-03-16 20:41:15 Re: pgsql: Support opfamily members in get_object_address
Previous Message Stephen Frost 2015-03-16 20:22:55 Re: Additional role attributes && superuser review