Received: from golem.pgsql.com (w148.z064003068.lax-ca.dsl.cnc.net [64.3.68.148]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eB7FcCP72240; Thu, 7 Dec 2000 10:38:12 -0500 (EST) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (localhost.localdomain [127.0.0.1]) by golem.pgsql.com (Postfix) with ESMTP id 55C1817C5E; Thu, 7 Dec 2000 15:59:29 +0000 (UTC) Message-ID: <3A2FB3E1.373766F8@alumni.caltech.edu> Date: Thu, 07 Dec 2000 15:59:29 +0000 From: Thomas Lockhart Organization: Yes X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.15-4mdksmp i686) X-Accept-Language: en MIME-Version: 1.0 To: Ivan =?iso-8859-1?Q?Hern=E1ndez?= , Hackers List Cc: pgsql-docs@postgresql.org Subject: Re: organization file References: <3A2FABD5.19E279BA@alumni.caltech.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200012/13 X-Sequence-Number: 60 > hi, yes a was talking about the first: the file format of tables. I was > reading about diferent file organizations (structures): sequential, heal, > ring, multi ring, etc... afaik most of the files are sequential in nature, with some record updates happening in the middle to mark records as "obsolete". So data is added on to the end, which is why running VACUUM is so important. > I look for some info in the documentation but i > didn't find nothing, also i'm interested about the recovery system of > postgresql.... i hope that you can give me some hints about where i can > look for it.... In previous releases, since all files are written sequentially the recovery system is very simple. For the upcoming 7.1 release with WAL, there is likely more done, but I'm not familiar with the details. Somebody want to write a (short) description? I'll include it in the docs... - Thomas