Re: [BUGS] PostGreSQL Alpha Question - Mailing list pgsql-hackers

From
Subject Re: [BUGS] PostGreSQL Alpha Question
Date
Msg-id 6b1d164058933f063dae8bd98eb94df3
Whole thread Raw
List pgsql-hackers
> Can anyone please give me a solution?  I *need* to have this solution
> working - we are using it for a very large scale project, and I was
> supposed to have this up-and-running yesterday.
>
> I would appreciate any help, comments, or suggestions you may be able to
> give.  At this point, I have spent 6 days on it, and I have lost all
> chance of becoming hopeful...

We have problems on alpha linux, and people are working on it.  Here is
a patch I got from someone several days ago that has a new s_lock.h for
alpha linux.  He also reports problems after this.  Please feel free to
contact him and work together to get this port working.

---------------------------------------------------------------------------


From melhiser@viper.co.union.nc.us Thu Nov  6 19:13:32 1997
Received: from viper.co.union.nc.us (co.union.nc.us [199.90.44.2])
    by candle.pha.pa.us (8.8.5/8.8.5) with ESMTP id TAA08995
    for <maillist@candle.pha.pa.us>; Thu, 6 Nov 1997 19:13:28 -0500 (EST)
Received: (from melhiser@localhost)
    by viper.co.union.nc.us (8.8.5/8.8.5) id UAA28831
    for maillist@candle.pha.pa.us; Thu, 6 Nov 1997 20:08:40 -0500
From: Travis Melhiser <melhiser@viper.co.union.nc.us>
Message-Id: <199711070108.UAA28831@viper.co.union.nc.us>
Subject: Re: [PORTS] Port Bug Report: Apppears to have a problem with compiling a portion of code dealing with locking
memory
To: maillist@candle.pha.pa.us (Bruce Momjian)
Date: Thu, 6 Nov 1997 20:08:40 -0500 (EST)
In-Reply-To: <199711052237.RAA14881@candle.pha.pa.us> from "Bruce Momjian" at Nov 5, 97 05:37:12 pm
Content-Type: text
Status: OR

> We have having trouble getting Alpha-Linux working with PostgreSQL
> because of the processor specific stuff in storage/s_lock.h.
>

I have fixed the ASM pieces in stoarage/s_lock.h
for the alpha.

I'll submit those here as well, but now that the compile
happens cleanly, I get an error while trying to run initdb.

Here it is as follows:

initdb: using /usr/local/pgsql/lib/local1_template1.bki.source as input to create the template database.
initdb: using /usr/local/pgsql/lib/global1.bki.source as input to create the global classes.
initdb: using /usr/local/pgsql/lib/pg_hba.conf.sample as the host-based authentication control file.

We are initializing the database system with username postgres (uid=508).
This user will own all the files and must also own the server process.

initdb: creating template database in /usr/local/pgsql/data/base/template1
Running: postgres -boot -C -F -D/usr/local/pgsql/data -Q template1
WARN:BuildFuncTupleDesc: function mkoidname(opaque, opaque) does not exist
initdb: could not create template database
initdb: cleaning up by wiping out /usr/local/pgsql/data/base/template1


------------
This doesn't appear to be related to the s_lock.h problem, is it?
when I do:
           nm postgres |grep mkoidname
I get:
           0000000120109f60 T mkoidname
           0000000120109f68 t mkoidname..ng

Do you have any hints on where I might start looking?

Here is the s_lock.h file, I was not sure how you wanted the diff, so I
just sent the entire piece.

Thanks,
    Travis

#################################################################

--
Bruce Momjian
maillist@candle.pha.pa.us

pgsql-hackers by date:

Previous
From: "Gord Pusnik"
Date:
Subject: [none]
Next
From: Marc Howard Zuckman
Date:
Subject: Performance surprise