| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
| Cc: | PgHacker <pgsql-hackers(at)postgresql(dot)org>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: pgstat wait timeout (RE: contrib/cache_scan) |
| Date: | 2014-03-12 14:42:03 |
| Message-ID: | 11970.1394635323@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com> writes:
> WARNING: pgstat wait timeout
> WARNING: pgstat wait timeout
> WARNING: pgstat wait timeout
> WARNING: pgstat wait timeout
> Once I got above messages, write performance is dramatically
> degraded, even though I didn't take detailed investigation.
> I could reproduce it on the latest master branch without my
> enhancement, so I guess it is not a problem something special
> to me.
> One other strangeness is, right now, this problem is only
> happen on my virtual machine environment - VMware ESXi 5.5.0.
> I couldn't reproduce the problem on my physical environment
> (Fedora20, core i5-4570S).
We've seen sporadic reports of that sort of behavior for years, but no
developer has ever been able to reproduce it reliably. Now that you've
got a reproducible case, do you want to poke into it and see what's going
on?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-03-12 14:48:13 | Re: db_user_namespace a "temporary measure" |
| Previous Message | Ashutosh Dhundhara | 2014-03-12 14:35:35 | GSoC 2014 |