PostgreSQL War Stories: Troubleshooting Production Challenges by Vikas & Rajesh

… One is scary plans and statistics out of it which is common like stands are not in place and things are not working. Then vacuum process no post conference is complete without vacuum {ts:65} being talked about. The third is connections then multi- transactions. This is a special feature. Then how memory utilization log contentions are taken there and then we'll also have a quick look on other challenges which might be very and cases … So symptoms are like {ts:187} slow running queries and then you will sometimes you will observe that there are more sequential scans happening or stale data. So these are common symptoms what we see but uh you know most common symptom is what we will say is uh whenever you try to debug the query {ts:206} first of all you need to find it out what exactly or which query is taking time. … Right? That is the {ts:268} important thing because most frequently we will see that if stats are out outdated then query will start giving you uh I mean optimizer will generate a bad plans and because of that you will see that query is getting affected right or you need to see uh there is a right {ts:287} index and which was you know uh the data was less in that table and there is a right index which was uh like getting picked by uh the queries till yesterday but today the data has been grow and now whatever the index right uh it is there on the table it is not actually working