Re: 7.2.1 segfaults.

From: Stephen Amadei <amadei(at)dandy(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: 7.2.1 segfaults.
Date: 2002-05-05 01:18:02
Message-ID: Pine.LNX.4.44.0205042110210.11954-100000@rastaban.dandy.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, 4 May 2002, Tom Lane wrote:

> Hmm. It looks like GetRawDatabaseInfo is reading a zero for the VARSIZE
> of datpath, and then computing -4 (which strncpy will take as a huge
> unsigned value) as the string length to copy. You could try applying
> a patch like this, in src/backend/utils/misc/database.c (about line
> 225 in current sources):

Wierd.

> However this really shouldn't be needed; I'm wondering whether the
> database's row in pg_database has been clobbered somehow. If so,
> it probably won't get much further before dying.

Good point. And deleting the $PGDATA directory and recreating it
fixed it without a patch.

> Two questions: does the same thing happen for all available databases?
> Have you tried to create a database with a nonstandard location
> (nondefault datpath)?

No... I was creating the database in /usr/local/pgsql/data and then
'cp -aRp'ing it into the chroot. So I had two copies of the same corrupt
database.

Thanks for the help.

----Steve
Stephen Amadei
Dandy.NET! CTO
Atlantic City, NJ

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Stephen Amadei 2002-05-05 01:40:42 Re: Why does Postgres need the /bin/sh?
Previous Message Tom Lane 2002-05-04 14:53:55 Re: Why does Postgres need the /bin/sh?