X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 53E59DB86E; Thu, 17 Nov 2005 05:19:30 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 07910-05-2; Thu, 17 Nov 2005 09:19:30 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from mx-2.sollentuna.net (mx-2.sollentuna.net [195.84.163.199]) by svr1.postgresql.org (Postfix) with ESMTP id 6E77BDB4CF; Thu, 17 Nov 2005 05:19:27 -0400 (AST) Received: from ALGOL.sollentuna.se (janus.sollentuna.se [62.65.68.67]) by mx-2.sollentuna.net (Postfix) with ESMTP id 242948F28C; Thu, 17 Nov 2005 10:19:29 +0100 (CET) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Subject: Re: [PERFORM] Help speeding up delete Date: Thu, 17 Nov 2005 10:19:28 +0100 Message-ID: <6BCB9D8A16AC4241919521715F4D8BCE6C7BF2@algol.sollentuna.se> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [pgsql-www] [PERFORM] Help speeding up delete thread-index: AcXrU4k7PjwS8+z1TDi66qZLjnVilgABDMAQ From: "Magnus Hagander" To: "Christopher Kings-Lynne" , "Simon Riggs" Cc: , "Tom Lane" , "Steve Wampler" , "Postgres-performance" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[AWL=0.000] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200511/108 X-Sequence-Number: 8823 > > Perhaps we should put a link on the home page underneath LATEST=20 > > RELEASEs saying > > 7.2: de-supported > >=20 > > with a link to a scary note along the lines of the above. > >=20 > > ISTM that there are still too many people on older releases. > >=20 > > We probably need an explanation of why we support so many=20 > releases (in=20 > > comparison to licenced software) and a note that this does=20 > not imply=20 > > the latest releases are not yet production (in comparison=20 > to MySQL or=20 > > Sybase who have been in beta for a very long time). >=20 > By the way, is anyone interested in creating some sort of=20 > online repository on pgsql.org or pgfoundry where we can keep=20 > statically compiled pg_dump/all for several platforms for 8.1? >=20 > That way if someone wanted to upgrade from 7.2 to 8.1, they=20 > can just grab the latest dumper from the website, dump their=20 > old database, then upgrade easily. But if they're upgrading to 8.1, don't they already have the new pg_dump? How else are they going to dump their *new* database? > In my experience not many pgsql admins have test servers or=20 > the skills to build up test machines with the latest pg_dump,=20 I don't, but I still dump with the latest version - works fine both on linux and windows for me...=20 > etc. (Seriously.) In fact, few realise at all that they=20 > should use the 8.1 dumper. That most people don't know they should use the new one I understand though. But I don't see how this will help against that :-) //Magnus