Re: [HACKERS] [PATCHES] [COMMITTERS] pgsql: Change FETCH/MOVE

2006-09-03 Thread Bruce Momjian
Tom Lane wrote:
 Bruce Momjian [EMAIL PROTECTED] writes:
  Tom Lane wrote:
  There is *no* credible use case for this (hint: MOVE FORWARD/BACKWARD
  ALL does not need this to work for 2G tables).
 
  Already done because of bad coding.  You want the TODO item removed too?
 
 As I said, I see no use case for it.  Maybe if Moore's Law holds up for
 another five or ten years, it'll look like a useful feature then ...

Removed.

-- 
  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDBhttp://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [HACKERS] [PATCHES] [COMMITTERS] pgsql: Change FETCH/MOVE

2006-09-02 Thread Bruce Momjian
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]
  EnterpriseDBhttp://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


Re: [HACKERS] [PATCHES] [COMMITTERS] pgsql: Change FETCH/MOVE to use int8.

2006-09-02 Thread Tom Lane
Bruce Momjian [EMAIL PROTECTED] writes:
 Tom Lane wrote:
 There is *no* credible use case for this (hint: MOVE FORWARD/BACKWARD
 ALL does not need this to work for 2G tables).

 Already done because of bad coding.  You want the TODO item removed too?

As I said, I see no use case for it.  Maybe if Moore's Law holds up for
another five or ten years, it'll look like a useful feature then ...

regards, tom lane

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings