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

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

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

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2006-09-03 01:11:51
Subject: Re: Postgres tracking - the pgtrack project
Previous:From: Bruce MomjianDate: 2006-09-02 23:58:35
Subject: Re: Backend SSL configuration enhancement

pgsql-committers by date

Next:From: Bruce MomjianDate: 2006-09-03 01:15:40
Subject: pgsql: Fix LLONG_MAX define used by new int64 FETCH/MOVE patch.
Previous:From: Bruce MomjianDate: 2006-09-03 00:46:41
Subject: pgsql: Remove unnecessary copyObject() call in update (values) code.

pgsql-patches by date

Next:From: Bruce MomjianDate: 2006-09-03 01:16:21
Subject: Re: [COMMITTERS] pgsql: Change FETCH/MOVE to use int8.
Previous:From: Bruce MomjianDate: 2006-09-03 00:46:19
Subject: Re: [HACKERS] extension for sql update

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