From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
---|---|
To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | stopping single-user standby |
Date: | 2014-07-13 20:53:47 |
Message-ID: | EC9A686C-950B-4E8D-9E0A-08D1639398C3@elevated-dev.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Oops. I was setting up a clone of a db for testing purposes. Accidentally copied in a recovery.conf. Then ran a script I have which actually does some maintenance by running pg in single-user, but of course the sql commands do not run and the script never terminates. So, yeah, I've now got pg in standby mode *and* single user.
- Can't do a normal kill on the server, it doesn't respond to that.
- Can't pg_ctl stop it because that doesn't work on a server running single-user.
- Can't pg_ctl promote it either.
I'm sure I can kill -9 this one, because there's no activity (it cannot even connect to the primary, because it's not reachable from here). But I'm just wondering if there's any more graceful way out of this little fubar. (Version is 9.3.4)
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
(303) 722-0567 voice
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2014-07-14 02:07:55 | Re: wal archive showing zero size |
Previous Message | John Scalia | 2014-07-11 17:56:16 | Re: WAL segment management on a standby |