| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Cursors and backwards scans and SCROLL |
| Date: | 2003-03-09 21:04:28 |
| Message-ID: | 1047243868.28251.217.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
> I'm presently leaning to #2, even though it exposes implementation
> details. I'm open to discussion though. Any preferences? Other ideas?
How about a variable that turns on or off spec enforcement (case #1 or
#2). On for 7.4, off for 7.5 the next release, and make it disappear
after that.
Enforcing spec seems like the least confusing mode to operate under,
especially given it could break simply by changing the plan -- which
happens automagically (seemingly random).
--
Rod Taylor <rbt(at)rbt(dot)ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-03-09 21:18:10 | Re: Cursors and backwards scans and SCROLL |
| Previous Message | Josh Berkus | 2003-03-09 20:59:35 | Re: [SQL] Cursors and backwards scans and SCROLL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-03-09 21:18:10 | Re: Cursors and backwards scans and SCROLL |
| Previous Message | Josh Berkus | 2003-03-09 20:59:35 | Re: [SQL] Cursors and backwards scans and SCROLL |