Re: [HACKERS] PostGreSQL v6.2.1 for Linux Alpha - Mailing list pgsql-hackers

From Kenji T. Hollis
Subject Re: [HACKERS] PostGreSQL v6.2.1 for Linux Alpha
Date
Msg-id Pine.BSF.3.95.980212010600.27046B-100000@Gawain.Houston-InterWeb.COM
Whole thread Raw
In response to Re: [HACKERS] PostGreSQL v6.2.1 for Linux Alpha  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] PostGreSQL v6.2.1 for Linux Alpha  (The Hermit Hacker <scrappy@hub.org>)
Re: [HACKERS] PostGreSQL v6.2.1 for Linux Alpha  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
Bruce:

> The problem here is that it can't find the function to make/use the
> index.  Try using initdb --debug to get more output, and see what is
> says about the mkoidname function creation.  Looks like pg_proc is not
> working, because a scan is returning nothing.  mkoidname is function
> used to index pg_attribute.  If you do initdb with --noclean, is
> data/template1/pg_proc indeed zero bytes.  Try adding a define to the
> postgres.h
>
> #define long int
>
> and see if it works.  Maybe the 64-bit longs are causing problems, and
> we have to fix them or change to ints.

Okay, I can try this.  In the current version of Postgres, when I run
"initdb --debug", I get the following output:

> CREATED relation pg_description with OID 17847
> Commit End
Amopen: relation pg_description. attrsize 63
create attribute 0 name objoid len 4 num 1 type 26
create attribute 1 name description len -1 num 2 type 25
> Amclose: relation (null).
> initdb: could not create template database
initdb: cleaning up by wiping out /usr/local/pgsql/data/base/template1

Installing the "#define long int" gives about 40 pages of errors.

> Make sure you turn on Assert checking in configure so it may give you an
> earlier error.

I have no idea of how to do set this in configure.  Configure has no
option to do this.

> These are very hard to debug because there is no running system to run
> tests on, and it is all very inter-related.

I can give access to my Alpha, but I have to talk to the person I am
dealing with.  I *will not* give access to this machine with a complete
stranger via E-Mail.

> My lib/local1_template1.bki.source has the following two lines for this
> function:
>
> insert OID = 949 ( mkoidname PGUID 11 f t f 2 f 911 "26 19" 100 0 0 100 foo bar)
> declare index pg_attribute_relid_attnam_index on pg_attribute using btree(mkoidname(attrelid, attname) oidname_ops)

Exact carbon-copy of mine.

> That is all the ideas I have for now.  Would like to get it working.

So would I.  Bruce, If you would like access to the Postgres machine,
please feel free to give me a call tomorrow.

-- Ken
------
   =========================================================================
      Houston InterWeb Design, Inc.     ||      Office: +1 (713) 627-9494
      Lead Programmer/Designer          ||         Fax: +1 (713) 627-2744
      C++, Windows, and Web Programming ||       Pager: +1 (713) 727-2529
   =========================================================================
               Home page URL: http://www.houston-interweb.com/


pgsql-hackers by date:

Previous
From: "Kenji T. Hollis"
Date:
Subject: Re: [HACKERS] PostGreSQL v6.2.1 for Linux Alpha
Next
From: t-ishii@sra.co.jp
Date:
Subject: configure fails on PPC/Linux