pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedWAL logs and segment files
4+ messages / 4 participants
[nested] [flat]
* WAL logs and segment files
@ 2004-02-19 17:12 Eduardo Leva <eeeggg499@netscape.net>
2004-02-20 20:29 ` Re: WAL logs and segment files Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 1 reply; 4+ messages in thread
From: Eduardo Leva @ 2004-02-19 17:12 UTC (permalink / raw)
To: pgsql-admin
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.
Pd. Sorry about my poor english. I speak spanish every day of my 3rd.
world's life...
Sigan adelante... Saludos.
Eduardo Leva
Programador
Santa Fe Argentina.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: WAL logs and segment files
2004-02-19 17:12 WAL logs and segment files Eduardo Leva <eeeggg499@netscape.net>
@ 2004-02-20 20:29 ` Bruce Momjian <pgman@candle.pha.pa.us>
2004-02-20 22:05 ` Re: WAL logs and segment files kaolin fire <cognosco@tentacle.net>
2004-02-21 00:10 ` Re: WAL logs and segment files scott <scott@QNET.COM>
0 siblings, 2 replies; 4+ messages in thread
From: Bruce Momjian @ 2004-02-20 20:29 UTC (permalink / raw)
To: Eduardo Leva <eeeggg499@netscape.net>; +Cc: pgsql-admin
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
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: WAL logs and segment files
2004-02-19 17:12 WAL logs and segment files Eduardo Leva <eeeggg499@netscape.net>
2004-02-20 20:29 ` Re: WAL logs and segment files Bruce Momjian <pgman@candle.pha.pa.us>
@ 2004-02-20 22:05 ` kaolin fire <cognosco@tentacle.net>
1 sibling, 0 replies; 4+ messages in thread
From: kaolin fire @ 2004-02-20 22:05 UTC (permalink / raw)
To: pgsql-admin
If you know where I can get a 1.5e+11 terabyte drive, I'd love to hear
it. ;)
-kaolin fire
-http://erif.org/code/fallingup/
On Feb 20, 2004, at 12:29 PM, Bruce Momjian wrote:
> 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
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: WAL logs and segment files
2004-02-19 17:12 WAL logs and segment files Eduardo Leva <eeeggg499@netscape.net>
2004-02-20 20:29 ` Re: WAL logs and segment files Bruce Momjian <pgman@candle.pha.pa.us>
@ 2004-02-21 00:10 ` scott <scott@QNET.COM>
1 sibling, 0 replies; 4+ messages in thread
From: scott @ 2004-02-21 00:10 UTC (permalink / raw)
To: Bruce Momjian <pgman@candle.pha.pa.us>; +Cc: eeeggg499@netscape.net; pgsql-admin
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
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2004-02-21 00:10 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-02-19 17:12 WAL logs and segment files Eduardo Leva <eeeggg499@netscape.net>
2004-02-20 20:29 ` Bruce Momjian <pgman@candle.pha.pa.us>
2004-02-20 22:05 ` kaolin fire <cognosco@tentacle.net>
2004-02-21 00:10 ` scott <scott@QNET.COM>
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