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

Re: [PORTS] PostgreSQL pre-7.1 Linux/Alpha Status...

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Ryan Kirkpatrick <pgsql(at)rkirkpat(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-ports(at)postgresql(dot)org
Subject: Re: [PORTS] PostgreSQL pre-7.1 Linux/Alpha Status...
Date: 2001-01-23 04:46:56
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-ports
How are you on Alpha now?

> 	I have had the time to test today's (12/19) snapshot on my
> Linux/Alpha and the good news is that only two regression tests are
> failing. The bad news is that these regression tests do not fail on
> Linux/Intel. :( [1]
> 	Specifically, the oid and misc regression tests failed. Here are
> the gory details:
> oid: Inserting a negative oid should wrap that oid around to an unsigned
>      value, but instead pgsql just spits it back out with an error
>      message. i.e.:
> ...
> ERROR:  oidin: error reading "-1040": value too large
>      Probably not a major problem (who inserts negative oids?), but I
>      could be wrong. Hopefully it has an easy fix.
> misc: This one is nasty... Any attempts to use the '*' operator in the
>       context of inheritance causes pgsql to lose its mind and wander off
>       into the weeds never to be seen again. Example from 'misc' tests:
> SELECT, FROM person* p;
> pqReadData() -- backend closed the channel unexpectedly.
>         This probably means the backend terminated abnormally
>         before or while processing the request.
> connection to server was lost
>       Definitely needs to be fixed, but I have a feeling it will not be
>       easy.
> Other than those two issues, everything seems to run great. I would go
> digging into the source to find the source of these problems, but I
> thought I would throw it out to the list first. [2]
> 	Therefore, if anyone has any ideas as to what is failing, how to
> fix it, or at least a general direction to head in (i.e. look in these
> source files...), please speak up. If you want more information on the
> above problems, feel free to ask. Just tell me what you want, and if it is
> not obvious, how to get it.
> 	Looking forward to a new version pgsql that compiles out of the
> box on Linux/Alpha! TTYL.
> [1] For those who missed my poor attempt at a joke... I mean that the
> Linux/Alpha regression failures are specific to that platform, and
> therefore my problem to solve, not a more general problem I could leave to
> the pg-hackers to solve....
> [2] That, and I am definitely not familiar with the pgsql source, so it
> would probably take me a while to make any headway if I just started
> digging with out any direction...
> ---------------------------------------------------------------------------
> |   "For to me to live is Christ, and to die is gain."                    |
> |                                            --- Philippians 1:21 (KJV)   |
> ---------------------------------------------------------------------------
> |   Ryan Kirkpatrick  |  Boulder, Colorado  |   |
> ---------------------------------------------------------------------------

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to


pgsql-ports by date

Next:From: Ryan KirkpatrickDate: 2001-01-23 14:49:48
Subject: Re: [PORTS] PostgreSQL pre-7.1 Linux/Alpha Status...
Previous:From: Yutaka tanidaDate: 2001-01-23 04:11:13
Subject: Re: (Cygwin) postmaster shutdown problem

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2001-01-23 04:47:40
Subject: Re: PL/Python (was: Re: [GENERAL] Re: Trigger)
Previous:From: Bruce MomjianDate: 2001-01-23 04:43:06
Subject: Re: User names

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