Обсуждение: Postgres SQL 6.3.2

Поиск
Список
Период
Сортировка

Postgres SQL 6.3.2

От
Gavin
Дата:
Hi

Please reply to gavin@space4u.com as i am not on the postgresql mailing
list (yet)

I compiled PostgreSQL 6.3.2 on my Alpha running linux.
with egcs-2.91.57 (thats 1.1b)
I got a few warnings but nothing that looked to bad ..

when running initdb as user postgres i get the following :

[postgres@sigi pgsql]$ initdb
initdb: using /usr/local/pgsql/lib/local1_template1.bki.source as input
to crea.
initdb: using /usr/local/pgsql/lib/global1.bki.source as input to create
the gl.
initdb: using /usr/local/pgsql/lib/pg_hba.conf.sample as the host-based
authent.

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

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

Any Ideas what that could be ?

Regards

Gavin Woodhatch
Space4u.com


Re: Postgres SQL 6.3.2

От
Peter Rye
Дата:
>>>>> "Gavin" == Gavin  <gavin@space4u.com> writes:

    Gavin> Hi Please reply to gavin@space4u.com as i am not on the
    Gavin> postgresql mailing list (yet)

    Gavin> I compiled PostgreSQL 6.3.2 on my Alpha running linux.  with
    Gavin> egcs-2.91.57 (thats 1.1b) I got a few warnings but nothing that
    Gavin> looked to bad ..

<snip>

    Gavin> Any Ideas what that could be ?

I posted here recently with another set of problems related to PostgreSQL.
I compiled mine using egcs-1.1b, but I used the source and patches from Red
Hat SRPM.

Clearly there are a few problems to be sorted out with Postgres on
Linux-Alpha. I tried postgresql.v6.4-BETA2.tar.gz however the compile
failed due to some problems with some inline asm.

The good news is that there are a number of people actively working on
these problems and there should be fixes available in the not too distant
future. I'm afraid fixing Postgres is beyond my ability.

I have been in touch with Ryan Kirkpatrick who feels that he may have a
patch available in a few days.