Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

I see a wealth of system administration questions about database servers (performance tuning, backup, recovery, re-indexing, etc). I suspect that these should be on not stackoverflow. Or are all things database acceptable simply because so much programming is database-oriented?

If the consensus is that these questions need to move, I'll post some links here so y'all can help me close/move them to the right site.

postgres is unbearably sluggish after a 130MB pg_restore. how to fix?

How do I fix Postgres so it will start after an abrupt shutdown?

Why is PostgreSQL so slow on Windows?

PostgreSQL restore and backup solution

PostgreSQL sequential scan on tiny table slow

Increase Query Speed in PostgreSQL

How to optimize slow delete query (delete data which is not used in another table) in Postgresql

How to optimize my PostgreSQL DB for prefix search?

Postgresql Tracing

share|improve this question
If the question is about writing sql queries, then it should stay here. If it is about tuning and setup, then they belong on SF. – jjnguy Feb 1 '11 at 3:20
@Justin: And the new DBA site is supposed to fit in there somehow as well. – BenV Feb 1 '11 at 3:22
@Justin: That's what I thought... actually with table design and query writing being a bit of a grey area. Clearly setting up database connections from (programming language of choice) is on-topic, and index design is SF material. But it's the last group I'm trying to raise awareness of, the ones that are squarely in the setup/performance tuning/backup and disaster recovery scenarios. – Ben Voigt Feb 1 '11 at 3:23
@BenV (let's see how long it is before someone confuses us): I guess DBA is where database design and stored procedure questions go, along with performance tuning. While backup and disaster recovery probably still belong on SF. But for right now it's possible to move questions to SF and not to DBA. – Ben Voigt Feb 1 '11 at 3:25
@BenVoigt: Ha, I didn't even notice when I wrote my initial comment! Hmm, I bet that has something to do with why I didn't get notified from your comment... – BenV Feb 1 '11 at 3:38
@Ben Voigt, that depend if you think the database design should drive the app design, or the app design should drive the database design. – Ian Ringrose Feb 2 '11 at 9:37
Writing stored procs is progamming so should be on SO – Ian Ringrose Feb 2 '11 at 9:38

The problem is that a lot of developers think of the “DBA” as system admin person that does the backups and setup user permissions.

Or think of the DBA being a person that considers the database to be the centre of the world, applications just to be a way to get data into their database and stored procs to be the answer to all programming problems. (And the DBA being the person that sets the rule that all 3rd party applications must be rewritten to use oracle, before they are allowed in their company, regardless of what the end user department that wishes to buy the application thinks)

Therefore it is unreasonable to expect programmers to ask database development questions on a site that is “owned” by DBAs.

I wish to ask other members of my “tribe” questions, not just other people the happen to use the some software….

share|improve this answer
So how do the questions I identified fit into that? I think they're all in the "backups and setup user permissions" vein, and therefore belong on a DBA or server admin site. – Ben Voigt Feb 1 '11 at 14:03
@Ben, A question like "PostgreSQL sequential scan on tiny table slow" could be asked by a programmer wanting to know if the design of his software should be changed, or by a DBA about an existing system that he has to "baby sit". In the first case, changing how PostgreSQL is being used is an option if there is not an easy fix to PostgreSQL, in the 2nd case the only option is to change how PostgreSQL is set up. So the some question asked by a member of a different "tribe" can have very different correct answers depending on the "tribe". – Ian Ringrose Feb 1 '11 at 14:11

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .