On 1/8/14 3:50 PM, Alvaro Herrera wrote:
> Yeah, this makes a lot more sense. What this is saying is that it's
> waiting for the I/O-lock on the pg_clog page to be released. In other
> words there is some other process holding that lock, which is supposed
> to be reading the page, but for some reason it's failing to do that
> timely. I guess you would need to get backtraces from all processes to
> see which one differs (i.e. which one has the lock and is trying to do
> something but not doing it).
I got only two, and they both looked like this, unfortunately. I'll try
to find the offender should this happen again.
In the meanwhile I'll be happy to provide more information if someone
has any ideas.
Regards,
Marko Tiikkaja
