| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | amutu(at)amutu(dot)com |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13900: stop standby failed with writer process hang(happen 3 times in 2 days) |
| Date: | 2016-01-30 07:22:43 |
| Message-ID: | CACjxUsOfQSPvkhiq=3A_SnvrJovuSV8Z5SPWTNAY9rW=6s5yrQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sat, Jan 30, 2016 at 8:13 AM, <amutu(at)amutu(dot)com> wrote:
> I am updating my 3 database from pg9.3 to pg9.5,but may find a bug for the
> bgwriter of pg9.3.I can't stop all the stand by process,even for immediate
> stop mode and kill -9,the writer process still there,with ps state "Ds" (D
> Marks a process in disk (or other short term, uninterruptible) wait) .google
> say the only method to clean the "Ds" process is rebooting the system.
> truss say no info for the process,and procstat say the process is calling
> the poll system call in the kernel.
There is no way for PostgreSQL to cause this. In all cases where I have
personally seen such behavior there was either failing storage hardware or a
driver with a bug (which I was always able to fix with the appropriate firmware
or driver upgrade).
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jov | 2016-01-30 07:35:56 | Re: BUG #13900: stop standby failed with writer process hang(happen 3 times in 2 days) |
| Previous Message | amutu | 2016-01-30 07:13:46 | BUG #13900: stop standby failed with writer process hang(happen 3 times in 2 days) |