Обсуждение: initdb problems
Well, initdb doesn't give the same errors, but it's still failing. Now it's just saying: initdb: could not create template database initdb: cleaning up by wiping out /usr/local/dbase/data/base/template1 with no other indication that it's failing. Heres the last bit of the debug: Inserting null Insert Begin InsertOneTuple oid 1219, 14 attrs End InsertOneTuple, objectid=1219 Insert End > Transaction End Amclose: relation (null). > <inhrel oid> <inhparent oid> <inhseqno int4> > initdb: could not create template database initdb: cleaning up by wiping out /usr/local/dbase/data/base/template1 [postgres@maidast pgsql]$ Now, looking at local1_template1.bki.source it's the pg_inherits definition that's failing. I don't know how the bki source works so I'm not much help here, but I can't see anything obviously wrong. -- Peter T Mount peter@retep.org.uk or petermount@earthling.net Main Homepage: http://www.retep.org.uk PostgreSQL JDBC Faq: http://www.retep.org.uk/postgres
At 10:49 AM 98.8.2 +0100, Peter T Mount wrote: >Well, initdb doesn't give the same errors, but it's still failing. Now >it's just saying: > >initdb: could not create template database >initdb: cleaning up by wiping out /usr/local/dbase/data/base/template1 > >with no other indication that it's failing. Heres the last bit of the >debug: > >Inserting null >Insert Begin >InsertOneTuple oid 1219, 14 attrs >End InsertOneTuple, objectid=1219 >Insert End > >> Transaction End >Amclose: relation (null). >> <inhrel oid> ><inhparent oid> ><inhseqno int4> > >> initdb: could not create template database >initdb: cleaning up by wiping out /usr/local/dbase/data/base/template1 >[postgres@maidast pgsql]$ > >Now, looking at local1_template1.bki.source it's the pg_inherits >definition that's failing. I don't know how the bki source works so I'm >not much help here, but I can't see anything obviously wrong. I have tried to reproduce your problem but failed using recent sources (my anon CVS is working now!). I reinstalled everything, removed $PGDATA and ran initdb (I did not turn on MULTIBYTE). I'm using FreeBSD 2.2.6-RELEASE. -- Tatsuo Ishii t-ishii@sra.co.jp
I got the same problem, running ldconfig namually solves this.
Oleg
On Sun, 2 Aug 1998, Tatsuo Ishii wrote:
> Date: Sun, 2 Aug 1998 22:27:59 +0900
> From: Tatsuo Ishii <t-ishii@sra.co.jp>
> To: Peter T Mount <peter@retep.org.uk>,
> PostgreSQL Hackers List <hackers@postgreSQL.org>
> Subject: Re: [HACKERS] initdb problems
>
> At 10:49 AM 98.8.2 +0100, Peter T Mount wrote:
> >Well, initdb doesn't give the same errors, but it's still failing. Now
> >it's just saying:
> >
> >initdb: could not create template database
> >initdb: cleaning up by wiping out /usr/local/dbase/data/base/template1
> >
> >with no other indication that it's failing. Heres the last bit of the
> >debug:
> >
> >Inserting null
> >Insert Begin
> >InsertOneTuple oid 1219, 14 attrs
> >End InsertOneTuple, objectid=1219
> >Insert End
> >
> >> Transaction End
> >Amclose: relation (null).
> >> <inhrel oid>
> ><inhparent oid>
> ><inhseqno int4>
> >
> >> initdb: could not create template database
> >initdb: cleaning up by wiping out /usr/local/dbase/data/base/template1
> >[postgres@maidast pgsql]$
> >
> >Now, looking at local1_template1.bki.source it's the pg_inherits
> >definition that's failing. I don't know how the bki source works so I'm
> >not much help here, but I can't see anything obviously wrong.
>
> I have tried to reproduce your problem but failed using recent
> sources (my anon CVS is working now!). I reinstalled everything,
> removed $PGDATA and ran initdb (I did not turn on MULTIBYTE).
> I'm using FreeBSD 2.2.6-RELEASE.
> --
> Tatsuo Ishii
> t-ishii@sra.co.jp
>
>
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
On Mon, 3 Aug 1998, Oleg Bartunov wrote: > I got the same problem, running ldconfig namually solves this. ldconfig solved an earlier but completely different problem - sadly. -- Peter T Mount peter@retep.org.uk or petermount@earthling.net Main Homepage: http://www.retep.org.uk PostgreSQL JDBC Faq: http://www.retep.org.uk/postgres