Skip site navigation (1) Skip section navigation (2)

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

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Change FETCH/MOVE
Date: 2006-09-03 13:37:41
Message-ID: 200609031337.k83Dbfl05181@momjian.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackerspgsql-patches
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> 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   bruce(at)momjian(dot)us
  EnterpriseDB    http://www.enterprisedb.com

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

In response to

pgsql-hackers by date

Next:From: Jeroen T. VermeulenDate: 2006-09-03 14:27:47
Subject: Re: Optimizing prepared statements
Previous:From: Gregory StarkDate: 2006-09-03 11:41:37
Subject: Re: Optimizing prepared statements

pgsql-committers by date

Next:From: User AndrewdDate: 2006-09-03 15:28:55
Subject: pgbuildfarm - client-code: Don't ignore files listed in a cvsignore file
Previous:From: Bruce MomjianDate: 2006-09-03 13:37:38
Subject: pgsql: Remove: < * Change LIMIT/OFFSET and FETCH/MOVE to use int8

pgsql-patches by date

Next:From: Tom LaneDate: 2006-09-03 16:08:58
Subject: Re: CSStorm occurred again by postgreSQL8.2
Previous:From: Michael GlaesemannDate: 2006-09-03 11:51:46
Subject: Re: [HACKERS] Interval aggregate regression failure (expected seems

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group