Re: problems with pg_dump... with postmaster really

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: problems with pg_dump... with postmaster really
Date: 2002-05-23 15:05:19
Message-ID: 200205231205.19449.martin@bugs.unl.edu.ar
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Jue 23 May 2002 11:58, Tom Lane wrote:
> =?iso-8859-1?q?Mart=EDn=20Marqu=E9s?= <martin(at)bugs(dot)unl(dot)edu(dot)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(at)unl(dot)edu(dot)ar
Programador, Administrador, DBA | Centro de Telematica
Universidad Nacional
del Litoral
-----------------------------------------------------------------

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message ktt 2002-05-23 15:06:00 pattern search
Previous Message Andrew Perrin 2002-05-23 15:01:17 Re: DBD::Pg: Placeholders not working