On Fri, Feb 5, 2010 at 9:50 PM, The Fuzzy Chef <fuzzy(at)fuzzychef(dot)org> wrote:
> Just had a very odd thing happen with an 8.4.2 database, and am
> concerned it's an undiagnosed bug:
> (1) created and dropped the same database 10-15 times in the course of
> running some tests.
> (2) at one point, dropdb hung. Indefinitely.
> (3) attempts to pg_cancel_backend on the DROP DATABASE process were
> futile. yet no other queries were accessing that database according to
> (4) pg_ctl -m fast did not shut down the server.
> (5) pg_ctl -m immediate did shut it down.
> (5a) realized pgbouncer was still running. shut it down as well.
> (6) on restart, the server took several minutes to *start* recover mode.
> then it got to a certain log segment, and hung indefinitely.
> (7) killed postgres
> (8) restarted again. this time the server came up in about 20s, and is
> behaving normally. The deleted database is not there.
> RHEL 5
> PostgreSQL 8.4.2, installed from yum.postgresql.org
> 8 databases and about 10G of data on the server
> pgbouncer running but NOT connected to the dropped database, just to two
> I've made a full copy of my PGDATA directory if anyone wants me to test
It's too bad you didn't capture a stack backtrace at step #3 or step
#6. If you manage to reproduce the problem, that would be a good
thing to try to get.
In response to
pgsql-bugs by date
|Next:||From: Josh Berkus||Date: 2010-02-07 00:47:30|
|Subject: Re: Possible stability issue: permanent hang on dropdb|
|Previous:||From: Robert Haas||Date: 2010-02-06 22:36:27|
|Subject: Re: BUG #5305: Postgres service stops when closing Windows session|