From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
---|---|
To: | josh(at)agliodbs(dot)com, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_ctl -m fast failing? |
Date: | 2003-03-07 20:19:08 |
Message-ID: | 200303071319.08332.pgsql@bluepolka.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Friday March 7 2003 11:56, Josh Berkus wrote:
> Tom,
>
> > No, I'd not expect the second stop to fail; and I can't reproduce any
> > such problem here.
>
> I've had it happen once.
I've seen this many times when a bug like that described below was in play
during shutdown. It's never been convenient to pin it down.
> > The known bug might cause the *first* stop to fail; it basically
> > triggers if you have a client that sits idle for a long time (while
> > other sessions are doing work) and still remains idle after the
> > shutdown command comes.
>
> So ... the workaround for 7.2.4 would be to have a server-side script
> hunt for idle connections after shutdown and kill -9 them?
There's a very small patch posted recently that fixes the problem, assuming
you can apply it.
Ed
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-03-07 20:24:38 | Re: division by zero |
Previous Message | Pam Wampler | 2003-03-07 20:13:48 | Re: division by zero |