X-Original-To: pgsql-hackers@postgresql.org Received: from houston.familyhealth.com.au (unknown [203.59.48.253]) by postgresql.org (Postfix) with ESMTP id BAFD6474E42 for ; Sun, 9 Mar 2003 21:33:34 -0500 (EST) Received: (from root@localhost) by houston.familyhealth.com.au (8.11.6/8.11.6) id h2A2XbL58957 for pgsql-hackers@postgresql.org; Mon, 10 Mar 2003 10:33:37 +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 h2A2XK758766; Mon, 10 Mar 2003 10:33:20 +0800 (WST) Message-ID: <011701c2e6ad$69d06170$6500a8c0@fhp.internal> From: "Christopher Kings-Lynne" To: "Doug McNaught" Cc: , "Tom Lane" References: <21621.1047242111@sss.pgh.pa.us><00e201c2e6ab$317eb9e0$6500a8c0@fhp.internal> Subject: Re: Cursors and backwards scans and SCROLL Date: Mon, 10 Mar 2003 10:33:18 +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/330 X-Sequence-Number: 36576 > > I'd be in favour of creating whole sets of backwards-compatibility GUC's > > whenever we break backwards compatibility. > > > > eg. > > use_72_compat = yes > > use_73_compat = yes > > That sounds like a recipe for a maintenance nightmare to me. We only have to keep them for one major version, say. eg. 7.3 release would remove the 71_compat option... Chris