X-Original-To: pgsql-performance@postgresql.org Received: from houston.familyhealth.com.au (unknown [203.59.48.253]) by postgresql.org (Postfix) with ESMTP id D3E3B475AFF for ; Thu, 20 Mar 2003 22:51:31 -0500 (EST) Received: (from root@localhost) by houston.familyhealth.com.au (8.11.6/8.11.6) id h2L3pZN23698 for pgsql-performance@postgresql.org; Fri, 21 Mar 2003 11:51:35 +0800 (WST) (envelope-from chriskl@familyhealth.com.au) Received: from mariner (mariner.internal [192.168.0.101]) by houston.familyhealth.com.au (8.11.6/8.9.3) with SMTP id h2L3pV723599; Fri, 21 Mar 2003 11:51:31 +0800 (WST) Message-ID: <08ac01c2ef5d$3487fec0$6500a8c0@fhp.internal> From: "Christopher Kings-Lynne" To: , References: <200303210909.56451.shridhar_daithankar@persistent.co.in> Subject: Re: Page Size in Future Releases Date: Fri, 21 Mar 2003 11:51:51 +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.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-scanner: scanned by Inflex 0.1.5c - (http://www.inflex.co.za/) X-Archive-Number: 200303/150 X-Sequence-Number: 1448 > > I have records about 881 byte + 40 byte (header) = 921. > > > > 8k page size / 921 bytes per record is ONLY 8 records........... > > You can tweak it yourself at compile time in some header file and that should > work but that is a point of diminising results as far as hackers are > concerned. As far as I'm aware the 8k page size has nothing to do with speed and everything to do with atomic writes. You can't be guaranteed that the O/S and hard drive controller will write anything more than 8K in an atomic block... Chris