I am using acts-as-taggle-on in a Rails app that I've hosted on Heroku. Heroku has a free Postgresql database that's limited to 10,000 rows. I was surprised to find that I surpassed the row limit, and upon examining the Tags and Taggings tables automatically created by acts-as-taggable-on, I found that my Tags table has 3,302 rows, but my Taggings table has a surprisingly large 17,103 rows.
Is there an explanation for the large number of rows in my Taggings table and any best practices about reducing the size?
I am using acts-as-taggle-on in a Rails app that I've hosted on Heroku. Heroku has a free Postgresql database that's limited to 10,000 rows. I was surprised to find that I surpassed the row limit, and upon examining the
TagsandTaggingstables automatically created byacts-as-taggable-on, I found that my Tags table has 3,302 rows, but my Taggings table has a surprisingly large 17,103 rows.Is there an explanation for the large number of rows in my Taggings table and any best practices about reducing the size?