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
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers pgsql-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

Browse pgsql-committers by date

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

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeroen T. Vermeulen 2006-09-03 14:27:47 Re: Optimizing prepared statements
Previous Message Gregory Stark 2006-09-03 11:41:37 Re: Optimizing prepared statements

Browse pgsql-patches by date

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