Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL crashes with Qmail-SQL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Devogelaere <michael(at)digibel(dot)be>
Cc: Jan Wieck <janwieck(at)yahoo(dot)com>, Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, Justin Clift <justin(at)postgresql(dot)org>, PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL crashes with Qmail-SQL
Date: 2002-01-24 18:45:47
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Michael Devogelaere <michael(at)digibel(dot)be> writes:
> On Thu, Jan 24, 2002 at 01:11:39PM -0500, Tom Lane wrote:
>> What showed up in the postmaster log when this happened?  I would like
>> *exact* error message texts, not approximations.
> Nothing. I disabled all logging since the database responded too slowly
> with logging turned on. So i cannot help you on this.

If you're not going to be cooperative, then I don't see how you expect
us to fix the problem.

FWIW, I don't believe for a moment that /dev/null'ing the postmaster log
improves performance measurably.  I've done plenty of profiling in my
time, and never seen any indication that it's an issue; at least not at
the default verbosity level.

>> What happened when you tried to connect with psql?  Again, exact, not
>> approximate.
> psql: connectDBStart() -- connect() failed: No such file or directory
> 	Is the postmaster running locally
> 	and accepting connection on Unix socket ...

No such file??  Hard to believe that that could happen while the
postmaster was still running.  Unless something else had decided to
delete the socket file from /tmp.  The postmaster certainly would not
do it.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Marc G. FournierDate: 2002-01-24 18:47:37
Subject: Re: 7.1.4
Previous:From: Denis PerchineDate: 2002-01-24 18:28:14
Subject: Re: 7.1.4

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group