Re: WAL segments (names) not in a sequence - Mailing list pgsql-hackers

From German Becker
Subject Re: WAL segments (names) not in a sequence
Date
Msg-id CALyjCLsAvEHrOTNtxTj6t_tRZFUbChHiwdVctH5mRja7LYny-w@mail.gmail.com
Whole thread Raw
In response to Re: WAL segments (names) not in a sequence  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: WAL segments (names) not in a sequence  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
<div dir="ltr">Thanks Amit, I understand now. Is there a way to know/predict how many prealocated segments will there
bein a certain moment? What does it deppend on?</div><div class="gmail_extra"><br /><br /><div class="gmail_quote"> On
Fri,May 24, 2013 at 12:46 PM, Amit Langote <span dir="ltr"><<a href="mailto:amitlangote09@gmail.com"
target="_blank">amitlangote09@gmail.com</a>></span>wrote:<br /><blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px#ccc solid;padding-left:1ex"><div class="im">> I didn't quite understand what you mean by
that...But anyways so do you<br /> > people think this sequence number overlap is "normal" ?<br /><br /></div>There
is"no overlap" at all. The newer segments that you see are<br /> "pre-allocated" ones. They have not been written to
yet.<br/><br /> From the "ls -l pg_xlog" output that you  sent, it can be seen that<br /> segments starting from
000000010000000E000000A8through<br /> 00000001000000100000007E have been pre-allocated (at that point of<br /> time)
and000000010000000E000000A7 is currently being written to. Just<br /> look at the modified times in your "ls -l"
listing.<br/> 000000010000000E000000A7 has May 22 15:32 (the latest writes seem to<br /> have happened to this segment)
whereaspre-allocated ones seem to have<br /> around May 22 12:05 to 12:15 (which are yet to be written to).<br /><br />
Doesthat help?<br /><br /> --<br /> Amit Langote<br /></blockquote></div><br /></div> 

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: visibilitymap_set and checksums
Next
From: Simon Riggs
Date:
Subject: Re: visibilitymap_set and checksums