Thread: Redo record at high number

Redo record at high number

From
"Jeff Boes"
Date:
We have noticed this line in our server log:

Redo record at (5, 4209179252); Undo record at (0, 0); Shutdown TRUE

That second number seems awfully high; should this give us cause for
concern?

--
Jeff Boes                                             vox 616.226.9550
Database Engineer                                     fax 616.349.9076
Nexcerpt, Inc.                                      jboes@nexcerpt.com

Re: Redo record at high number

From
Tom Lane
Date:
"Jeff Boes" <jboes@nexcerpt.com> writes:
> We have noticed this line in our server log:
> Redo record at (5, 4209179252); Undo record at (0, 0); Shutdown TRUE

> That second number seems awfully high; should this give us cause for
> concern?

Looks fishy to me too --- the offset shouldn't exceed 24 bits AFAIR.
Vadim, what do you think?

            regards, tom lane

Re: Redo record at high number

From
Tom Lane
Date:
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM> writes:
>> Looks fishy to me too --- the offset shouldn't exceed 24 bits AFAIR.

> Log record ptr is 4 bytes for log file ID and 4 bytes for record offset.
> # of segmets in log file (2^32 - 1) / 2^24 = 255
> Max offset *in segment* is 2^24 , but max offset *in log file*
> is 255 * 2^24 = 4278190080

You're right, I'm wrong, it's a false alarm.  Sorry for the noise.

            regards, tom lane

Re: Redo record at high number

From
"Mikheev, Vadim"
Date:
> We have noticed this line in our server log:
>
> Redo record at (5, 4209179252); Undo record at (0, 0); Shutdown TRUE
>
> That second number seems awfully high; should this give us cause for
> concern?

You'll see (6, <small number>) soon.

Vadim

Re: Redo record at high number

From
"Mikheev, Vadim"
Date:
> > We have noticed this line in our server log:
> > Redo record at (5, 4209179252); Undo record at (0, 0); Shutdown TRUE
>
> > That second number seems awfully high; should this give us cause for
> > concern?
>
> Looks fishy to me too --- the offset shouldn't exceed 24 bits AFAIR.
> Vadim, what do you think?

Log record ptr is 4 bytes for log file ID and 4 bytes for record offset.
# of segmets in log file (2^32 - 1) / 2^24 = 255
Max offset *in segment* is 2^24 , but max offset *in log file*
is 255 * 2^24 = 4278190080

Vadim