Trying to reduce database size

[gabter1]

I am trying to reduce database size using the recommended deleting position records where ideal_battery_range_km is NULL. However, I lose all elevation data with this. It seems that whenever teslamate records the range, it doesn't record the elevation.
Any recommendations as to reducing the positions table but keeping elevation data?
After 2 years and 40000 km, database size is 1,5GB.

[brianmay]

recommended deleting position records where ideal_battery_range_km is NULL

I am not aware of anybody making that recommendation.

I see a recommendation concerning making queries, but that is different to deleting the data in the database.

https://docs.teslamate.org/docs/development/#streaming-api-data--positions-table-usage-in-dashboard-queries

Any recommendations as to reducing the positions table but keeping elevation data?

Any deletion is going to result in loss of data. If you are desperate, it really depends what data you are willing to lose.

Why is 1.5GB database a problem?

[gabter1]

Yeah, sorry for not wording correctly.
I am making a backup of the database daily and thought that would be a good idea. I don't need data every second for trips from years ago, so I was hoping for some cleaning up :)