1. Based on discussion on the postgres developers' list on this topic, I would believe 20ms to be an extreme case. Take the last digit off for a more typical number.
2. If it's still too long, well that's why the bug only asks for the longest query to be explained. :-)
Two points:
1. Based on discussion on the postgres developers' list on this topic, I would believe 20ms to be an extreme case. Take the last digit off for a more typical number.
2. If it's still too long, well that's why the bug only asks for the longest query to be explained. :-)