oopsreply-to-all
-- Forwarded message --
From: Chris Redekop
Date: Wed, Nov 2, 2011 at 8:41 AM
Subject: Re: [HACKERS] Hot Standby startup with overflowed snapshots
To: Simon Riggs
Sure, I've got quite a few logs lying around - I've attached 3 of 'em...let
m
On Fri, Oct 28, 2011 at 3:42 AM, Chris Redekop wrote:
> On a side note I am sporadically seeing another error on hotstandby startup.
> I'm not terribly concerned about it as it is pretty rare and it will work
> on a retry so it's not a big deal. The error is "FATAL: out-of-order XID
> insertio
On Thu, Oct 27, 2011 at 6:55 PM, Simon Riggs wrote:
> It seems cheap to add in a call to LogStandbySnapshot() after each
> call to pg_stop_backup().
>
> Does anyone think this case is worth adding code for? Seems like one
> more thing to break.
Why at that particular time?
It would maybe nice if
Sorry..."designed" was poor choice of words, I meant "not unexpected".
Doing the checkpoint right after pg_stop_backup() looks like it will work
perfectly for me, so thanks for all your help!
On a side note I am sporadically seeing another error on hotstandby startup.
I'm not terribly concerned
On Thu, Oct 27, 2011 at 10:09 PM, Chris Redekop wrote:
> hrmz, still basically the same behaviour. I think it might be a *little*
> better with this patch. Before when under load it would start up quickly
> maybe 2 or 3 times out of 10 attemptswith this patch it might be up to 4
> or 5 time
hrmz, still basically the same behaviour. I think it might be a *little*
better with this patch. Before when under load it would start up quickly
maybe 2 or 3 times out of 10 attemptswith this patch it might be up to 4
or 5 times out of 10...ish...or maybe it was just fluke *shrug*. I'm stil
On Thu, Oct 27, 2011 at 5:26 PM, Chris Redekop 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
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.
Chris Redekop's recent report of slow startup for Hot Standby has made
me revisit the code there.
Although there isn't a bug, there is a missed opportunity for starting
up faster which could be the source of Chris' annoyance.
The following patch allows a faster startup in some circumstances.
The
