Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > >> This patch has broken half the buildfarm, and I've still not seen a > >> rationale why we need to make such a change at all. > > > Fixed with attached patch. The use case for this was not FETCH, but > > MOVE for > 2gig tables. > > There is *no* credible use case for this (hint: MOVE FORWARD/BACKWARD > ALL does not need this to work for >2G tables). It is not worth the > extra computational cycles that it imposes on every machine whether they > use the feature or not, and it is certainly not worth the developer time > we're expending to fix this poorly written patch. Please revert it.
Already done because of bad coding. You want the TODO item removed too? -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
