Re: Postgres db corrupted ?

From: "John P(dot) Looney" <valen(at)tuatha(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Mendola Gaetano <mendola(at)bigfoot(dot)com>, postgres <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Postgres db corrupted ?
Date: 2003-07-31 08:21:31
Message-ID: 1059639691.7984.2405.camel@cosimo.hosting365.ie
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wed, 2003-07-30 at 15:26, Tom Lane wrote:
> "Mendola Gaetano" <mendola(at)bigfoot(dot)com> writes:
> > ""John P. Looney"" <valen(at)tuatha(dot)org> writes:
> >> bbadmin | | SQL_ASCII
>
> > For sure a way to obtain this inconsistence is delete the owner of
> > a db and voila' a DB result to have no owner.
>
> Nope. I don't know how John got into this state, but it most definitely
> was not that way. Try it.

OK, it turns out that the cause was the shared hosting admin software
that was trying to add users and databases had some wierd problems
(hidden obscure shell scripts crashing out when it couldn't find an up
to date text dump of the pg_shadow file), which resulted in tables being
created, given specific sysids for users that weren't created.

Anyway, it looks like it wasn't a postgres bug that caused the
problems. If any field should be considered "not null" though, it's that
owner field!

John

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Peter Eisentraut 2003-07-31 09:01:24 Re: storage calculations
Previous Message Tom Lane 2003-07-31 02:49:25 Re: parallel regression test failure