perf: limit positions to set elevation for to last 10 days

[swiffer]

This limits the positions to set elevation for to the last 10 days greatly speeding up the query and reducing stress on the database.

fixes #4225

[netlify]

✅ Deploy Preview for teslamate ready!

Name	Link
🔨 Latest commit	be38045
🔍 Latest deploy log	https://app.netlify.com/sites/teslamate/deploys/67025315cba3f300086dc544
😎 Deploy Preview	https://deploy-preview-4228--teslamate.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[swiffer]

need support on this one - maybe someone with elixir knowledge can step in?

[JakobLichterfeld]

@brianmay Can you take a look into this PR? Would love to include this in next release as it greatly improve background performance on small hosts with large logging base.

[swiffer]

@JakobLichterfeld did it ! ✌️also having a local dev env now... this is ready.

Before you are releasing a new version - do you want to add a hint to the release mentioning availability of postgres 17 and also recommend users checking their current indexes by linking to an issue / discussion?

1.) Upgrade TeslaMate
2.) Ensure everything still working
3.) Create Backup
4.) Run Index Fix Script
5.) Create Backup
6.) Upgrade PostgreSQL to 17 in Docker
7.) Restore from Backup via updated Restore Guide

• we shouldn't wait with release that long as the docs have already been published.

[brianmay]

If I understand this correctly, the one tradeoff with this is if I can't run teslamate for some reason (e.g. hardware failure) for 10+ days, the elevations of the last drives may not be set.

Probably a reasonable tradeoff.

[swiffer]

If I understand this correctly, the one tradeoff with this is if I can't run teslamate for some reason (e.g. hardware failure) for 10+ days, the elevations of the last drives may not be set.

Probably a reasonable tradeoff.

true, but in this case you won't have any new data collected. so the potential case would be, hardware failure while driving and then maybe some elevation data updates missing. but in that case you're missing more than just that... think it's ok

[JakobLichterfeld]

@JakobLichterfeld did it ! ✌️also having a local dev env now... this is ready.

Awesome! Love to see it!

Before you are releasing a new version - do you want to add a hint to the release mentioning availability of postgres 17 and also recommend users checking their current indexes by linking to an issue / discussion?

Yeah, debating the best way to do it, perhaps including the index checker in the docs as well, but every additional script is a potential source of unrelated support issues.

• we shouldn't wait with release that long as the docs have already been published.

From what I get, the updated restore doc does not harm if used with postgres16 or before, innit?

[swiffer]

@JakobLichterfeld did it ! ✌️also having a local dev env now... this is ready.

Awesome! Love to see it!

Before you are releasing a new version - do you want to add a hint to the release mentioning availability of postgres 17 and also recommend users checking their current indexes by linking to an issue / discussion?

Yeah, debating the best way to do it, perhaps including the index checker in the docs as well, but every additional script is a potential source of unrelated support issues.

Agree - would like to avoid having it in the docs but maybe give a hint to users that we had cases and asking them to check their instance once in the release notes pointing to the issue?

• we shouldn't wait with release that long as the docs have already been published.

From what I get, the updated restore doc does not harm if used with postgres16 or before, innit?

Agree

[swiffer]

@JakobLichterfeld - rebased on latest master. should be ready for merge.