On Monday, June 23, 2014, AI Rumman <
rummandba@gmail.com> wrote:
Could someone please tell me why I am getting these in my log:
2014-06-23 00:00:00.031 CDT [11379][@] : [1-1]LOG: skipping analyze of "table1" --- lock not available
2014-06-23 00:00:00.056 CDT [11380][@] : [1-1]LOG: skipping analyze of "table1" --- lock not available
2014-06-23 00:00:00.081 CDT [11381][@] : [1-1]LOG: skipping analyze of "table1" --- lock not available
2014-06-23 00:00:00.106 CDT [11382][@] : [1-1]LOG: skipping analyze of "table1" --- lock not available
2014-06-23 00:00:00.131 CDT [11383][@] : [1-1]LOG: skipping analyze of "table1" --- lock not available
2014-06-23 00:00:00.156 CDT [11384][@] : [1-1]LOG: skipping analyze of "table1" --- lock not available
2014-06-23 00:00:00.181 CDT [11385][@] : [1-1]LOG: skipping analyze of "table1" --- lock not available
2014-06-23 00:00:00.206 CDT [11386][@] : [1-1]LOG: skipping analyze of "table1" --- lock not available
2014-06-23 00:00:00.231 CDT [11387][@] : [1-1]LOG: skipping analyze of "table1" --- lock not available
It means that something has a higher-than-typical lock on table1 which is blocking the analyze. It could be a CLUSTER or an REINDEX or something like that, but my best guess is that it is an autovacuum on that table that is doing it.
Based on the low time between the messages, I'd also speculate that there is an autovacuum in the same database being done for anti-wrap around purposes, and you are falling afoul of this:
It is probably nothing to worry about. The presence of LOG messages which have not been specifically requested doesn't mean you have a problem, it just means that if you *do* have an empirical problem, this would be a good place to start investigating it.
Cheers,
Jeff