X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 3E73AD1D4E7 for ; Sat, 21 Feb 2004 00:14:23 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 95491-10 for ; Fri, 20 Feb 2004 20:14:24 -0400 (AST) Received: from mx-i.qnet.com (mx-i.qnet.com [209.221.198.23]) by svr1.postgresql.org (Postfix) with ESMTP id 1B552D1D132 for ; Fri, 20 Feb 2004 20:14:21 -0400 (AST) Received: from cello.qnet.com ([209.221.198.10]) by mx-i.qnet.com with esmtp (Exim 4.30) id 1AuKmh-0001a5-Tz; Fri, 20 Feb 2004 16:14:19 -0800 Received: from scott (arc0-pool223-158.dial.qnet.com [209.221.223.158]) by cello.qnet.com (8.9.3/8.9.1) with SMTP id QAA06554; Fri, 20 Feb 2004 16:14:12 -0800 (PST) Message-ID: <001b01c3f80f$2fcd7de0$9edfddd1@scott> From: "scott" To: "Bruce Momjian" Cc: , "Cc:" References: <200402202029.i1KKTNJ22723@candle.pha.pa.us> Subject: Re: WAL logs and segment files Date: Fri, 20 Feb 2004 16:10:59 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/318 X-Sequence-Number: 12492 Take me off your list! You have the wrong scott! ----- Original Message ----- From: "Bruce Momjian" To: "Eduardo Leva" Cc: 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