Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Configuring BLCKSZ and XLOGSEGSZ (in 8.3)

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>,"Peter Eisentraut" <peter_e(at)gmx(dot)net>,<pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] Configuring BLCKSZ and XLOGSEGSZ (in 8.3)
Date: 2006-12-10 12:57:01
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
On Fri, 2006-12-08 at 13:18 -0500, Tom Lane wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)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             

In response to


pgsql-hackers by date

Next:From: Simon RiggsDate: 2006-12-10 13:00:06
Previous:From: Michael FuhrDate: 2006-12-10 05:50:05
Subject: psql display of Unicode combining characters in 8.2

pgsql-patches by date

Next:From: Inaam RanaDate: 2006-12-10 14:49:08
Subject: Re: Load distributed checkpoint
Previous:From: Tom LaneDate: 2006-12-09 17:57:40
Subject: Re: [DOCS] 8.2.0 pdf

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group