X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id F181FD1B4F4 for ; Fri, 21 Nov 2003 01:31:12 +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 58112-02 for ; Thu, 20 Nov 2003 21:30:45 -0400 (AST) Received: from houston.familyhealth.com.au (fhnet.arach.net.au [203.22.197.21]) by svr1.postgresql.org (Postfix) with ESMTP id E4645D1D5AF for ; Thu, 20 Nov 2003 21:30:40 -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 hAL1UboD000525; Fri, 21 Nov 2003 09:30:37 +0800 (WST) (envelope-from chriskl@familyhealth.com.au) Message-ID: <3FBD6CAA.7040500@familyhealth.com.au> Date: Fri, 21 Nov 2003 09:38:50 +0800 From: Christopher Kings-Lynne User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: Jan Wieck , Peter Eisentraut , PostgreSQL Development Subject: Re: Release cycle length References: <20031117202346.M731@ganymede.hub.org> <3FBB7F20.8050005@Yahoo.com> <6400.1069359578@sss.pgh.pa.us> In-Reply-To: <6400.1069359578@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: 200311/1159 X-Sequence-Number: 47447 > Yeah, I think the main issue in all this is that for real production > sites, upgrading Postgres across major releases is *painful*. We have > to find a solution to that before it makes sense to speed up the > major-release cycle. Well, I think one of the simplest is to do a topological sort of objects in pg_dump (between object classes that need it), AND regression testing for pg_dump :) Chris