this happens on 2 machines,and both use zfs,scrub say no error.
By now 2 machines,3 standby instances,I will try to reproduce it on linux.
2016=E5=B9=B41=E6=9C=8830=E6=97=A5 3:22 PM=EF=BC=8C"Kevin Grittner" <kgritt=
n@gmail.com>=E5=86=99=E9=81=93=EF=BC=9A
> On Sat, Jan 30, 2016 at 8:13 AM, <amutu@amutu.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 calli=
ng
> > 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 o=
r
> 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
>