Email or username:

Password:

Forgot your password?
mrcopperbeard's posts Post Back to profile
mrcopperbeard

Non pro #postgres user tip.

If you rewriting and optimizing some db queries in your service, you can spot latency degradation while deploying it. Reason may be in not actual query statistics, used to optimize previous query versions. So you can inspect new query plans, determine hanging tables and run analyze command on it
postgresql.org/docs/current/sq

19 September at 8:38 | Open on mastodon.ml
2 comments
mrcopperbeard

In my case I drop a few joins, deploy it, but join on other table, that I not even touched, started use seq scan instead of index. I saw x10 query degradation and rollback release.

After analyze query plans started use index again.

19 September at 8:41 | Open on mastodon.ml
mrcopperbeard

But after that I spotted a few more degradated queries. And rolled back release again. But after research I figured out that queries always have pikes on latency graphic at this time of day.

So the point is: keep calm and profile query behaviour not only for few hours, but for a couple days too.

19 September at 9:29 | Open on mastodon.ml
Go Up