Re: [HACKERS] Configuring BLCKSZ and XLOGSEGSZ (in 8.3) - Mailing list pgsql-patches

From Simon Riggs
Subject Re: [HACKERS] Configuring BLCKSZ and XLOGSEGSZ (in 8.3)
Date
Msg-id 1165755421.3839.778.camel@silverbirch.site
Whole thread Raw
In response to Re: [HACKERS] Configuring BLCKSZ and XLOGSEGSZ (in 8.3)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Configuring BLCKSZ and XLOGSEGSZ (in 8.3)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
On Fri, 2006-12-08 at 13:18 -0500, Tom Lane wrote:
> "Simon Riggs" <simon@2ndquadrant.com> writes:

> What I'm considering is having pg_resetxlog scan the pg_xlog directory
> and assume that any segment files present might have been used.

[Reading committed code...]

That's a very neat short cut - just using the file names rather than
trying to read the files themselves as the abortive patch a few months
back tried.

Question: What happens when we run out of LogIds? I know we don't wrap
onto the next timeline, but do we start from LogId=1 again? Looks to me
like we just fall on the floor right now.

We're probably not pressed for an answer... :-)

--
  Simon Riggs
  EnterpriseDB   http://www.enterprisedb.com



pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Configuring BLCKSZ and XLOGSEGSZ (in 8.3)
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Configuring BLCKSZ and XLOGSEGSZ (in 8.3)