X-Original-To: pgsql-advocacy-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 8767AD1D88B; Tue, 3 Feb 2004 04:51:39 +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 43185-04; Tue, 3 Feb 2004 00:51:36 -0400 (AST) Received: from houston.familyhealth.com.au (fhnet.arach.net.au [203.22.197.21]) by svr1.postgresql.org (Postfix) with ESMTP id 30CD6D1D52A; Tue, 3 Feb 2004 00:51:35 -0400 (AST) Received: from familyhealth.com.au (work-40.internal [192.168.0.40]) by houston.familyhealth.com.au (8.12.9p1/8.12.9) with ESMTP id i134p5VD016899; Tue, 3 Feb 2004 12:51:05 +0800 (WST) (envelope-from chriskl@familyhealth.com.au) Message-ID: <401F29BF.7060705@familyhealth.com.au> Date: Tue, 03 Feb 2004 12:55:27 +0800 From: Christopher Kings-Lynne User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: josh@agliodbs.com, Jan Wieck , pgsql-performance@postgresql.org, pgsql-advocacy@postgresql.org Subject: Re: [PERFORM] MySQL+InnoDB vs. PostgreSQL test? References: <200402020921.12076.josh@agliodbs.com> <401EFD98.2020402@Yahoo.com> <401F0FCD.70903@familyhealth.com.au> <200402021941.57516.josh@agliodbs.com> <11250.1075781322@sss.pgh.pa.us> <401F23F3.8080009@familyhealth.com.au> <11553.1075783437@sss.pgh.pa.us> In-Reply-To: <11553.1075783437@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/11 X-Sequence-Number: 3582 >>Out of interest, what is it about this particular task that's so hard? > > > Keeping track of multiple lockers in a fixed amount of disk space. Why not look at how InnoDB does it? Or is that not applicable?