PostgreSQL Minor Release Retention Policy

In a blog post, Devrim wrote: "This means, when there is new release available, we will delete n-3th one. This is a policy to keep the repo clean. This does not apply for PostgreSQL major releases”

I take it this actually means release and not version, right? For instance, last I checked we had 9.5.3-2, 9.5.4-1, and 9.5.4-2 in there. So if I know I’m on 9.5.4, I’m not automatically safe until 9.5.7… my package may disappear as soon as 9.5.5 if there is enough RPM release churn?

This makes it pretty unsafe to hardcode a full version specifier in e.g. a Dockerfile or other system meant to produce repeatable results, but I suppose people can just run their own package mirrors if they desire a different retention policy.

Just wanting some clarity on my interpretation, though. Thanks!

--
Jason Petersen
Software Engineer | Citus Data
303.736.9255
jason(at)citusdata(dot)com