From: scott <scott@QNET.COM>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: eeeggg499@netscape.net
Cc: Cc: <pgsql-admin@postgresql.org>
Subject: Re: WAL logs and segment files
Date: Fri, 20 Feb 2004 16:10:59 -0800
Message-ID: <001b01c3f80f$2fcd7de0$9edfddd1@scott> (raw)
References: <200402202029.i1KKTNJ22723@candle.pha.pa.us>
Take me off your list! You have the wrong scott!
----- Original Message -----
From: "Bruce Momjian" <pgman@candle.pha.pa.us>
To: "Eduardo Leva" <eeeggg499@netscape.net>
Cc: <pgsql-admin@postgresql.org>
Sent: Friday, February 20, 2004 12:29 PM
Subject: Re: [ADMIN] WAL logs and segment files
> Eduardo Leva wrote:
> > Hi, guys... I'm reading the version 7.3.4 documentation and I found
this: "
> >
> > "WAL logs are stored in the directory $PGDATA/pg_xlog, as a set of
segment
> > files, each 16 MB in size. Each segment is divided into 8 kB pages. The
> > log record headers are described in access/xlog.h; record content is
> > dependent on the type of event that is being logged. Segment files are
> > given ever-increasing numbers as names, starting at 0000000000000000.
The
> > numbers do not wrap, at present, but it should take a very long time to
> > exhaust the available stock of numbers. "
> >
> > in item 12.2 Implementation. The question is: How do I solve this
> > situation, the remarked situation? The answer is not in the docs.
Thanks.
>
> What situation do you need to solve? The wrapping? The documention
> states "a very long time", but it more of a joke. That number would be
> huge to wrap around and you would be updating your PostgreSQL version
> long before it would ever wrap.
>
> The number is actually an int8 that has a maximum value of:
>
> 18446744073709551616
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square, Pennsylvania
19073
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: scott@QNET.COM, pgman@candle.pha.pa.us, eeeggg499@netscape.net
Subject: Re: WAL logs and segment files
In-Reply-To: <001b01c3f80f$2fcd7de0$9edfddd1@scott>
References: <200402202029.i1KKTNJ22723@candle.pha.pa.us> <001b01c3f80f$2fcd7de0$9edfddd1@scott>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox