The Hermit Hacker wrote:
>
> On Wed, 24 May 2000, planx plnetx wrote:
>
> > I've remarked that postgresql-7.0 have two important bugs no, no...
> > I'll define its Problems.
> >
> > The first is that it is very subsceptible to ipc: it's true that sometimes
> > U need to do an ipcclean to remake it start
>
> This sounds like a Linux problem to me ... I've got v7.0 running on a
> server over here that is dealign with the Search engine for the PostgreSQL
> site (over 10million tuples in one table, indexing over 90k URLs) and the
> server has been running flawlessly for the past ~14days now, and what is
> only because that was the last time we rebooted it ...
We've been running 7.0 on a linux server since RC3 on a database with
over 40 million tuples without this problem (all 40 million tuples are
indexed on 3 fields). So I'm not sure I see how it can be concluded
that this is a linux problem.
> > The second is the very VERY important instability problem.
> > I explain me better: I've tried Postgres on different systems
> > (redhat6.0,6.1, mandrake7.0) and every time after that I make start the
> > postmaster 20 or 30 times in a week or 2, it begin to have a problem
> > with shared memory, but i do an ipcclean and go..., after when
> > postmaster run without problems if I do a createuser (from sqladmin) or
> > a createdb (from user) it give me the same problem like:
> >
> > ------------------------------------------------
> > FATAL 1: cannot create init file
> > mydatabasedirectory//base/mydb/pg_internal.init
> > ------------------------------------------------
> >
> > it happens after few times of correct running... and persist also if I
> > recompile again postgresql
I just restarted a different server 50 consecutive times and I cannot
reproduce this error either.
(Both these are Redhat 6.2. We also have postgreSQL 7.0 running on a
few Redhat 6.1 servers).
Karl DeBisschop