connection handling in 7.4.1

From: Scott Yeadon <scott(dot)yeadon(at)anu(dot)edu(dot)au>
To: pgsql-bugs(at)postgresql(dot)org
Subject: connection handling in 7.4.1
Date: 2004-01-20 22:37:55
Message-ID: 200401210937.55472.scott.yeadon@anu.edu.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

Postgres is part of the openSource repository DSpace which we are running here
at ANU. I upgraded from 7.4 to 7.4.1 on 17 January. Today (21/1) it appears
that either the number of connections has been reached (which is not possible
on my local install) or the database itself has locked up. Postmaster was
restarted on 20/1 so the problemt has taken 2 days to surface. I have not had
a chance to look much deeper into the problem as I don't expect to get time
to investigate until next week.

The log output postgres returned is as follows:
FATAL: the database system is shutting down

The application log is as follows:

Note that postgres is the only thing that has changed, no other software has
been updated. This did not occur under 7.4

A secondary issue is that postmaster will not shut down properly under 7.4.1,
I always have to use the "fast" shutdown mode. Has anything changed in the
connection handling, as if connections are not being released this could
easily cause the first problem? Again, this appears peculiar to 7.4.1.

Thanks.

Scott.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PostgreSQL Bugs List 2004-01-20 22:52:08 BUG #1057: psql sometimes does not flush its output
Previous Message PostgreSQL Bugs List 2004-01-20 20:44:30 BUG #1056: ecpg ignores WHENEVER NOT FOUND