From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: pgsql-hackers@postgresql.org
To: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Cursors and backwards scans and SCROLL
Date: Mon, 10 Mar 2003 10:17:26 +0800
Message-ID: <00e201c2e6ab$317eb9e0$6500a8c0@fhp.internal> (raw)
References: <21621.1047242111@sss.pgh.pa.us>
> 3. Create a runtime parameter (GUC variable) which when set causes us
> to assume SCROLL is present even if it's not stated. Setting this
> to TRUE would allow existing applications to work without modification;
> when it's FALSE, we'd enforce the spec behavior. The trouble with this
> is the TRUE setting would likely cause materialization costs to be paid
> in very many situations where the client has no intention of fetching
> backwards.
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
or something.
And then we can define all the things that those variables will affect.
That would mean that people can upgrade to new db engine (say 7.3) without
worrying about all the failures in their applications ( eg ''::int)...
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, pgsql-hackers@postgresql.org, tgl@sss.pgh.pa.us
Subject: Re: Cursors and backwards scans and SCROLL
In-Reply-To: <00e201c2e6ab$317eb9e0$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