<p></p>
<blockquote>
<p>I believe we should just ditch the old migrations, say every migration over 2 years old.</p>
</blockquote>
<p>What we do at betterplace.org is: We run <a href="https://github.com/jalkoby/squasher%C2%A0about">https://github.com/jalkoby/squasher about</a> once a year or so which gives us a single migration file which creates the DB in just the way that it would look like after running all single migrations. This still allows to run migrations and end up with a correct DB setup.</p>
<p>I did in fact try out to use squasher around last December/January for this project but ran into errors that looked like they are PostgreSQL related … or maybe had something to do with special indexes or primay keys(?) (It might be the same as the composite_primary_keys gem you guys talk about in the Rails6.1 branch).</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/3110#issuecomment-789684176">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLMZDNJXEVBLEST2PGDTBYULDANCNFSM4YFH7W4A">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AAK2OLPPGSC7TQD6CKMO2TTTBYULDA5CNFSM4YFH7W4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOF4IZ7UA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/issues/3110#issuecomment-789684176",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/3110#issuecomment-789684176",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>