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

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

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Change FETCH/MOVE to use int8.
Date: 2006-09-03 01:16:21
Message-ID: 200609030116.k831GLj11514@momjian.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackerspgsql-patches
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. +

Attachment: /bjm/diff
Description: text/x-diff (1.6 KB)

In response to

Responses

pgsql-hackers by date

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

pgsql-committers by date

Next:From: Bruce MomjianDate: 2006-09-03 01:22:56
Subject: pgsql: Fix case where "PM" to_timestamp() mask was eating too many
Previous:From: Bruce MomjianDate: 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 DunstanDate: 2006-09-03 01:23:01
Subject: Re: better support of out parameters in plperl
Previous:From: Tom LaneDate: 2006-09-03 00:56:33
Subject: Re: [COMMITTERS] pgsql: Change FETCH/MOVE to use int8.

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