Thanks for all the feedback guys. Just to throw another monkey wrench in
here - I've been playing with Simon's proposed solution of returning 0 when
the WAL positions match, and I've come to the realizatiion that even if
using pg_last_xact_insert_timestamp, although it would help, we still
wouldn'
> > Linas, could you capture the output of pg_controldata *and* increase the
> > log level to DEBUG1 on the standby? We should then see nextXid value of
> > the checkpoint the recovery is starting from.
>
> I'll try to do that whenever I'm in that territory again... Incidentally,
> recently there w
7:33 PM, Chris Redekop wrote:
> > > Linas, could you capture the output of pg_controldata *and* increase
> the
> > > log level to DEBUG1 on the standby? We should then see nextXid value of
> > > the checkpoint the recovery is starting from.
> >
> >
er load it cleared itself upI'm shooting in the dark here
Anyone have any suggestions/ideas/things to try?
On Mon, Oct 17, 2011 at 2:13 PM, Chris Redekop wrote:
> I can confirm that both the pg_clog and pg_subtrans errors do occur when
> using pg_basebackup instead of rsync. The da
> Chris, can you rearrange the backup so you copy the pg_control file as
> the first act after the pg_start_backup?
I tried this and it doesn't seem to make any difference. I also tried the
patch and I can no longer reproduce the subtrans error, however instead it
now it starts up, but never gets
>
> That isn't a Hot Standby problem, a recovery problem nor is it certain
> its a PostgreSQL problem.
>
Do you have any theories on this that I could help investigate? It happens
even when using pg_basebackup and it persists until another sync is
performed, so the files must be in some state that
> And I think they also reported that if they didn't run hot standby,
> but just normal recovery into a new master, it didn't have the problem
> either, i.e. without hotstandby, recovery ran, properly extended the
> clog, and then ran as a new master fine.
Yes this is correct...attempting to start
FYI I have given this patch a good test and can now no longer reproduce
either the subtrans nor the clog error. Thanks guys!
On Wed, Oct 26, 2011 at 11:09 AM, Simon Riggs wrote:
> On Wed, Oct 26, 2011 at 5:16 PM, Simon Riggs
> wrote:
> > On Wed, Oct 26, 2011 at 5:08 PM, Simon Riggs
> 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.
..or is it
actually as designed that it could take 10-ish minutes to start up even
after all clients have disconnected from the primary?
On Thu, Oct 27, 2011 at 11:27 AM, Simon Riggs wrote:
> On Thu, Oct 27, 2011 at 5:26 PM, Chris Redekop wrote:
>
> > Thanks for the patch Simon, but unf
any way I can...but
if you're not too worried about it then neither am I :)
On Thu, Oct 27, 2011 at 4:55 PM, Simon Riggs wrote:
> 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*
>
looks like the v3 patch re-introduces the pg_subtrans issue...
On Tue, Nov 1, 2011 at 9:33 AM, Simon Riggs wrote:
> On Thu, Oct 27, 2011 at 4:25 PM, Simon Riggs
> wrote:
>
> > StartupMultiXact() didn't need changing, I thought, but I will review
> further.
>
> Good suggestion.
>
> On review, S
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
okay, sorry I'm a little confused then. Should I be able to apply both the
v2 patch as well as the v3 patch? or is it expected that I'd have to
manually do the merge?
On Wed, Nov 2, 2011 at 1:34 AM, Simon Riggs wrote:
> On Wed, Nov 2, 2011 at 2:40 AM, Chris Redekop wrote:
>
On Wed, Nov 9, 2011 at 6:22 PM, Florian Pflug wrote:
> On Nov9, 2011, at 23:53 , Daniel Farina wrote:
> > I think a novice user would be scared half to death: I know I was the
> > first time. That's not a great impression for the project to leave
> > for what is not, at its root, a vast defect,
15 matches
Mail list logo
