From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Doug McNaught <doug@mcnaught.org>
Cc: pgsql-hackers@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Cursors and backwards scans and SCROLL
Date: Mon, 10 Mar 2003 10:33:18 +0800
Message-ID: <011701c2e6ad$69d06170$6500a8c0@fhp.internal> (raw)
References: <21621.1047242111@sss.pgh.pa.us>
<00e201c2e6ab$317eb9e0$6500a8c0@fhp.internal>
<m3y93oj6iw.fsf@varsoon.wireboard.com>
> > 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: chriskl@familyhealth.com.au, doug@mcnaught.org, pgsql-hackers@postgresql.org, tgl@sss.pgh.pa.us
Subject: Re: Cursors and backwards scans and SCROLL
In-Reply-To: <011701c2e6ad$69d06170$6500a8c0@fhp.internal>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox