Tom Lane wrote:
> momjian(at)postgresql(dot)org (Bruce Momjian) writes:
> > Log Message:
> > -----------
> > Change FETCH/MOVE to use int8.
> 
> 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.

-- 
  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

• Re: [COMMITTERS] pgsql: Change FETCH/MOVE to use int8. at 2006-09-03 00:56:33 from Tom Lane

Responses

• Re: [COMMITTERS] pgsql: Change FETCH/MOVE to use int8. at 2006-09-03 03:22:35 from Tom Lane

pgsql-hackers by date

Next:	From: Andrew Dunstan	Date: 2006-09-03 01:23:01
	Subject: Re: better support of out parameters in plperl
Previous:	From: Andrew Dunstan	Date: 2006-09-03 01:11:51
	Subject: Re: Postgres tracking - the pgtrack project

pgsql-committers by date

Next:	From: Bruce Momjian	Date: 2006-09-03 01:22:56
	Subject: pgsql: Fix case where "PM" to_timestamp() mask was eating too many
Previous:	From: Bruce Momjian	Date: 2006-09-03 01:15:40
	Subject: pgsql: Fix LLONG_MAX define used by new int64 FETCH/MOVE patch.

pgsql-patches by date

Next:	From: Andrew Dunstan	Date: 2006-09-03 01:23:01
	Subject: Re: better support of out parameters in plperl
Previous:	From: Tom Lane	Date: 2006-09-03 00:56:33
	Subject: Re: [COMMITTERS] pgsql: Change FETCH/MOVE to use int8.