Re: problems with pg_dump... with postmaster really - Mailing list pgsql-general

From Martín Marqués
Subject Re: problems with pg_dump... with postmaster really
Date
Msg-id 200205231205.19449.martin@bugs.unl.edu.ar
Whole thread Raw
In response to Re: problems with pg_dump... with postmaster really  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: problems with pg_dump... with postmaster really
List pgsql-general
On Jue 23 May 2002 11:58, Tom Lane wrote:
> =?iso-8859-1?q?Mart=EDn=20Marqu=E9s?= <martin@bugs.unl.edu.ar> writes:
> > On Jue 23 May 2002 11:50, Tom Lane wrote:
> >> No.  A backend crash is Postgres' fault, no matter what client software
> >> you're using.
> >
> > But that php client was compiled with the PostgreSQL 7.1.3 libpg library,
> > and now I have a new one. That doesn't matter?
>
> Not for this.  If a backend crashes, that's a backend bug, no matter
> *what* is talking to it.

OK. I thought it could have ben PHP because after installing I got a few
consecutive times this error until I restarted apache (with the mod_php) and
all went OK after.

At this moment I changed the ulimit to get the core files, ran pg_dumpall but
didn't get a problem with the backend.

What those this mean in the error:


pg_dump: query to obtain list of operators failed: server closed the
connection unexpectedly


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

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: problems with pg_dump... with postmaster really
Next
From: "Wm. G. Urquhart"
Date:
Subject: Re: Violation of NOT NULL