X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 3C8B8D1EA9D for ; Fri, 2 Apr 2004 07:04:14 +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 77782-07 for ; Fri, 2 Apr 2004 03:04:13 -0400 (AST) Received: from gpdnet.co.uk (gpdnet.plus.com [212.56.100.243]) by svr1.postgresql.org (Postfix) with ESMTP id 623A6D1EA89 for ; Fri, 2 Apr 2004 03:04:11 -0400 (AST) Received: from Spooler by gpdnet.co.uk (Mercury/32 v4.01a) ID MO001D53; 2 Apr 2004 08:07:59 +0100 Received: from spooler by gpdnet.co.uk (Mercury/32 v4.01a); 2 Apr 2004 08:07:44 +0100 Received: from gary (192.168.1.2) by gpdnet.co.uk (Mercury/32 v4.01a) with ESMTP ID MG001D52; 2 Apr 2004 08:07:39 +0100 From: "Gary Doades" To: pgsql-performance@postgresql.org Date: Fri, 02 Apr 2004 08:07:38 +0100 MIME-Version: 1.0 Subject: Re: PostgreSQL and Linux 2.6 kernel. Message-ID: <406D1F4A.27973.73B2299@localhost> In-reply-to: <23109.1080887530@sss.pgh.pa.us> References: <406C7956.17885.4B2DCD2@localhost> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/8 X-Sequence-Number: 6308 The post was not intended to be content-rich, just my initial feedback after only just switching to 2.6. Since I had largely given up on this particular line of attack using 2.4 I didn't think to do a detailed analysis at this time. I was also hoping that others would add to the discussion. As this could become important I will be doing more analysis, but due to the nature of the issue and trying to keep as many factors constant as possible, this may take some time. Cheers, Gary. On 2 Apr 2004 at 1:32, Tom Lane wrote: > "Gary Doades" writes: > > As a test in PosgreSQL I issued a statement to update a single column > > of a table containing 2.8 million rows with the values of a column in > > a table with similar rowcount. Using the above spec I had to stop the > > server after 17 hours. The poor thing was thrashing the hard disk and > > doing more swapping than useful work. > > This statement is pretty much content-free, since you did not show us > the table schemas, the query, or the EXPLAIN output for the query. > (I'll forgive you the lack of EXPLAIN ANALYZE, but you could easily > have provided all the other hard facts.) There's really no way to tell > where the bottleneck is. Maybe it's a kernel-level issue, but I would > not bet on that without more evidence. I'd definitely not bet on it > without direct confirmation that the same query plan was used in both > setups. > > regards, tom lane > > > -- > Incoming mail is certified Virus Free. > Checked by AVG Anti-Virus (http://www.grisoft.com). > Version: 7.0.230 / Virus Database: 262.6.5 - Release Date: 31/03/2004 >