Too many "Slow performance" meta tags

Question

Do we really need all these different meta tags for "Slow performance" like:

• performance
• postgresql-performance
• query-performance
• performance-tuning
• optimization
• query-optimization
• slow-log
  etc

Or can we merge some of them to maybe only use:

• performance (postgresql-performance, query-performance)
• optimization (performance-tuning, query-optimization)

Answer 1

I like where your head is at. I would rather not break down performance by database, just use multiple tags. I'm not sure how to find all the synonyms for everything (ex: slow-log) so I would need help identifying more synonyms

---

So, here's a thing: I went ahead and did this thinking "yeah, this is a good idea, let's keep things simple! YAY!" and wasn't actually considering that this has been discussed before :-(

• Should the optimization tag be re-purposed away from "query optimization" and towards "general" system-level optimization?
• Merge tag:postgresql-performance with tag:query-performance?

I pulled this trigger. Some things are now final and can't be undone:

1. query-optimization merged into optimization
2. query-performance merged into performance
3. postgresql-performance merged into performance
4. slow-log merged into performance
5. performance-testing into performance
6. performance-tuning into performance
7. pg-basebackup merged into backup
8. xtrabackup merged into backup
9. netbackup merged into backup

That was stupid on my part. I should have waited like a week at minimum. I, put simply, messed up. I let the community down by being too eager to do something good. I'm sorry guys (and gals).

---

Okay, some of the re-tagging has been undone thanks to Shog9 (community moderator) so some of the original tags are back. We'll have to re-do the tag-wikis, the mods have access to some of that information.