From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Chris Redekop <chris(at)replicon(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Hot Standby startup with overflowed snapshots |
Date: | 2011-10-27 17:27:51 |
Message-ID: | CA+U5nMKB0VZRH8U85cVeb-6OxAcw_1ipwkyYkVtZxcqRPxGG-g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Oct 27, 2011 at 5:26 PM, Chris Redekop <chris(at)replicon(dot)com> wrote:
> Thanks for the patch Simon, but unfortunately it does not resolve the issue
> I am seeing. The standby still refuses to finish starting up until long
> after all clients have disconnected from the primary (>10 minutes). I do
> see your new log statement on startup, but only once - it does not repeat.
> Is there any way for me to see what the oldest xid on the standby is via
> controldata or something like that? The standby does stream to keep up with
> the primary while the primary has load, and then it becomes idle when the
> primary becomes idle (when I kill all the connections)....so it appears to
> be current...but it just doesn't finish starting up
> I'm not sure if it's relevant, but after it has sat idle for a couple
> minutes I start seeing these statements in the log (with the same offset
> every time):
> DEBUG: skipping restartpoint, already performed at 9/95000020
OK, so it looks like there are 2 opportunities to improve, not just one.
Try this.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Attachment | Content-Type | Size |
---|---|---|
faster_hot_standby_startup_withsubxacts.v2.patch | application/octet-stream | 3.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-10-27 17:43:56 | Re: Bug in walsender when calling out to do_pg_stop_backup (and others?) |
Previous Message | Heikki Linnakangas | 2011-10-27 16:49:38 | Re: plpgsql versus long ELSIF chains |