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

Re: [HACKERS] Re: Tuple-valued datums on Alpha (was Re: 7.1 on DEC/Alpha)

From: Brent Verner <brent(at)rcfile(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ryan Kirkpatrick <rkirkpat(at)rkirkpat(dot)net>, pgsql-patches(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: Tuple-valued datums on Alpha (was Re: 7.1 on DEC/Alpha)
Date: 2000-12-27 23:05:55
Message-ID: 20001227180555.A6402@rcfile.org (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On 27 Dec 2000 at 16:50 (-0500), Tom Lane wrote:
| After further study, I realized that fetchatt() and a number of other
| places were not prepared to cope with 8-byte pass-by-value datatypes.
| Most of them weren't checking for cases they couldn't handle, either.
| 
| Here is a revised patch for you to try (this includes yesterday's patch
| plus more changes, so you'll need to reverse out the prior patch before
| applying this one).  NOTE you will need to do a full reconfigure and
| rebuild to make this fly --- I'd suggest "make distclean" to start.

excellent!

this patch fixes the SEGV problem in the regression tests. the only 
remaining failures, which are not due to SEGV, are:

  oid                  ... FAILED
  float8               ... FAILED
  geometry             ... FAILED

initial comments WRT failures:
  float8    fails only when building with gcc.
  oid       recall seeing one-liner change to correct this. will try.

many thanks,
  brent


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2000-12-27 23:10:07
Subject: Re: [HACKERS] Re: Tuple-valued datums on Alpha (was Re: 7.1 on DEC/Alpha)
Previous:From: Frank JoerdensDate: 2000-12-27 22:22:45
Subject: Re: PHP and PostgreSQL

pgsql-patches by date

Next:From: Tom LaneDate: 2000-12-27 23:10:07
Subject: Re: [HACKERS] Re: Tuple-valued datums on Alpha (was Re: 7.1 on DEC/Alpha)
Previous:From: Tom LaneDate: 2000-12-27 21:50:10
Subject: Re: [HACKERS] Re: Tuple-valued datums on Alpha (was Re: 7.1 on DEC/Alpha)

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