Re: Fix for FETCH FIRST syntax problems
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Peter Geoghegan <pg@bowt.ie>, Vik Fearing <vik.fearing@2ndquadrant.com>,
Andrew Gierth <andrew@tao11.riddles.org.uk>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2018-05-22T14:22:20Z
Lists: pgsql-hackers
On Tue, May 22, 2018 at 5:59 AM, Robert Haas <robertmhaas@gmail.com> wrote: > If we start routinely > back-patching things that fall into that category, we will certainly > manage to destabilize older releases on a regular basis. > Just because something is bad if done in excess doesn't mean specific moderate partaking is bad too. We actually did backpatch the NaN stuff and reverted that because, for me, it was a silent change of functioning behavior. I find the decision to back-patch this syntax oversight considerably more obvious than that one was. David J.
Commits
-
Fix SQL:2008 FETCH FIRST syntax to allow parameters.
- 89b09db01b43 9.3.24 landed
- 769e6fcd1a35 9.4.19 landed
- 3b0fb2529fdf 9.5.14 landed
- 7a0aa8d12ace 9.6.10 landed
- cf516dc9d690 10.5 landed
- 1da162e1f5a7 11.0 landed
-
SQL:2008 alternative syntax for LIMIT/OFFSET:
- 361bfc35724a 8.4.0 cited