Re: restoreing dumps fail

From: Martín Marqués <martin(at)bugs(dot)unl(dot)edu(dot)ar>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: restoreing dumps fail
Date: 2002-05-14 11:38:07
Message-ID: 200205140838.08045.martin@bugs.unl.edu.ar
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Lun 13 May 2002 23:34, Tom Lane wrote:
> =?iso-8859-1?q?Mart=EDn=20Marqu=E9s?= <martin(at)bugs(dot)unl(dot)edu(dot)ar> writes:
> > I'm trying to upgrade from 7.1.3 to 7.2.1 and after makeing a dump,
> > installing the new version (7.2.1) making the initdb as postgres, when I
> > try to dump all the data back to the database, and after some dump the
> > backend dies:
> >
> > NOTICE: Message from PostgreSQL backend:
> > The Postmaster has informed me that some other backend
> > died abnormally and possibly corrupted shared memory.

I went back to 7.1.3 because the server was in production, and couldn't wait
for me to solve the problem. I'll try to upgrade next week.

> Oh? What's in the postmaster log? Can you get a stack trace from
> the core file that the crashed backend left?

What I would like to know is what to do when I have these problems? Get the
core file and run a strace over it? Run gdb over the core?

Thanks.

--
Porqué usar una base de datos relacional cualquiera,
si podés usar PostgreSQL?
-----------------------------------------------------------------
Martín Marqués | mmarques(at)unl(dot)edu(dot)ar
Programador, Administrador, DBA | Centro de Telematica
Universidad Nacional
del Litoral
-----------------------------------------------------------------

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Martín Marqués 2002-05-14 13:25:44 Re: restoreing dumps fail
Previous Message Andrey Y. Mosienko 2002-05-14 10:19:10 postmaster core dumps with SPI_repalloc