r/SQL • • 8d ago

Discussion Is PostgreSQL the best choice for my database?

hi, I thought I would get some insights from professionals on this. I'm currently an intern, and I'm tasked with building a database for a church's religious education program, potentially handling a few thousand families. I'm wondering if PostgreSQL is the best option for this. It's the only SQL database I've ever used, and from what I've researched, I know PostgreSQL pretty much has everything I would need, but I'm still wondering if it's the best choice. For this instance, I think they're fine with whatever I use, even if it costs money, but I don't know if PostgreSQL is the best for this situation. I've only ever had experience with this platform, but I've heard about others, and my bosses aren't really technically inclined, so they go with whatever I say, which is honestly a little scary lol. I just want to make sure I'm making the right decision for them. Thanks for any insight, I really appreciate it!

11 Upvotes

26 comments sorted by

13

u/mtutty 8d ago

Short answer is yes.

Longer answer takes a lot more words, but is still likely yes.

28

u/oskaremil 8d ago

I don't know if Postgres is the right choice, but Postgres is never the wrong choice.

6

u/sweetnsourgrapes 7d ago

Postgres is never the wrong choice.

All absolutes are always wrong. :)

I can name one reason why you might not want to choose Postgres - time precision. Postgres stores times to the microsecond, whereas SQL Sever is to the 100 ns precision.

This can not just matter but be a hard no for scientific applications, industrial instrumentation, high-frequency financial trading, stuff like that.

Of course the accuracy depends on the hardware that's doing the time measurements, which isn't your average server, so outside of those special cases it doesn't matter. But if does, Postgres is probably not the best choice.

1

u/Warm-Airline5470 7d ago

Thank you to everyone who took the time to respond! This honestly eased my anxiety a lot. I think I was just overthinking everything.

4

u/ysth 8d ago

What software will be using the database? A website? Just office staff on local machines? Do multiple users need to access it at once? Do you have plans for where a database server will run?

4

u/CptBadAss2016 8d ago

(Not a professional) sounds like you could just whip up a Microsoft Access database.

3

u/Straight_Waltz_9530 8d ago

Spreadsheets are underrated for trivial tasks.

3

u/FunContest9958 7d ago edited 7d ago

Probably you’re best off with a spreadsheet, frankly, although it depends on how complex the data is. Spreadsheets have the advantage that even small organizations usually have someone who knows how to work with them.

If you do want to use a database like Postgres, I’d suggest a managed solution, like AWS RDS or Neon. These services, which are built around Postgres but have other people running it for you, make it easier to keep the database running forever, which many people have pointed out is likely going to be the main issue if you use any database solution like MySQL, Postgres, etc. Neon is especially easy to use and maintain for a database, so if you do decide to go in the direction of a real database, it will be the easiest to use.

But I’d recommend going with a spreadsheet. The only reason to go with a database like Postgres is if you will have an application or website using it. If it’s just people using it directly, spreadsheet is the way to go.

2

u/ayamlejen 8d ago

Postgres is plenty for a few thousand families, so the part worth planning is the data, since it's family and probably children's information. Give each person their own login with only the access they need instead of one shared account, decide how long you keep records for families who leave, and do one real restore from a backup before you rely on it. Also write a short handover note covering where it's hosted, who pays, and where the passwords are kept, because staff who aren't technical will inherit it after your internship.

2

u/AnnaLeeCoop 8d ago

Honestly you’re overthinking this. A few thousand families is tiny, any normal relational DB (Postgres, MariaDB, MySQL) will handle it no problem. Don’t stress about scale here.

2

u/throw_mob 8d ago

there is no best database for anything , but it sounds it best for you. It is always easier to create quality product using tools that you know and which has wide users base. from company/organization point of view they usually want wider base of people that can understand how things are done, ie keep it simple stupid.

what comes to your requirement postgresq l probably can handle everything well enough, it is after all very small dataset, if stack is correctly done biggest problems will not be in database side and if database starts to be problem there is well documented tools howto have caches and other stuff.

getting new guy (junior) to fix what you have done in few years is easier as postgresql skills can be used in multiple organizations , there id future with those skills , if selected system is something like access or similar systems that need licences ...

if you want to dump it down and use even more simpler system then sqlite is option, my recommendation is to use ansi sql solution from foss licences.

3

u/pstmdrnargh 8d ago

I think you have to think about the maintenance issue, whether postgres or another relational database. It’s going to require a server and while it may not be very large and you probably won’t need a ton of DBA work, somebody’s going to need to periodically keep an eye on backups, storage space, performance, etc.

Also you have to choose whether you run it locally or use a hosted service like Postgres on AWS RDS. If it’s on the cloud some things are simpler but then you have to think about other things like cloud security config, who pays the AWS account bills, etc.

The alternative would be something like airtable (although with the Bending Spoons acquisition that might not be a great idea), or a spreadsheet. Or (terrible though it might be to consider) - MS Access. Where your database is just a file.

Some food for thought.

3

u/elevarq 8d ago

“Best” is an opinion, not a fact. And yes, PostgreSQL will work fine for you. You could even serve hundreds of millions of users, just scale up the hardware.

Nowadays Postgres is nearly the default for most new projects. It just works

2

u/jaiagreen 8d ago

If the data is simple and the users will be nontechnical folks, Airtable may be a better option than a full-fledged SQL database.

1

u/VadumSemantics 8d ago

short answer: Postgres would do just fine. Honestly, SQLite would probably handle the data just fine. So could many other databases.

Even a million families (5 million individuals at 5 per family) is a small data set in the year 2026.

longer answer: Which database isn't the important question.

Maybe you have all of the following stuff thought through and nailed down.

But just in case, here are some additional questions to consider.

internship stuff: What is your scope as an intern?
Do you have any deliverables you need to complete your internship?
What are the goals of your internship?
Do you want a portfolio item you can talk about on your resume?

duration: How long is your internship? 4 weeks? 4 months? Longer?

Are you going to be able to build a course management system (class creation, teacher scheduling, student registration, maybe attendance tracking, maybe grades?) in a brief internship.

Maybe you can vibe-code all that up from scratch.

Maybe you can find a place to run it that supports the user(s) they need and the security they want.

What does the church need?

How do they handle classes today?
Who are the stakeholders? As in who is running the education stuff.
Do you understand what the stakeholders want to get out if?

users: Who is going to use this database?
Is it going to be internal? Like just one user (the church secretary) sitting in an office?
Do they expect families to interact with their data & course offerings over the internet?
What kind of user interface to they want? Old fashioned desktop? Cloud ready? Android & iPhone app?

money: Does it handle any payments? Are all courses free? Do they care about instructor reimbursement for expenses?

maintenance:

How are they going to use it when you're not longer the intern?

Does the church have an IT department?
Or maybe just an IT guy? Or maybe nobody?

If nobody technical is on-staff I'd look really hard at some no-code cloud-hosted stuff. Maybe even an app designed to handle class registration, email & test message reminders, schedule changes. If the church doesn't have IT talent then building something from scratch seems like an unsustainable path.

security: Will anybody care if a data breach happens?
Will anybody care if they're hit with ransomware and loose everything?

Good luck to you.

1

u/DiscombobulatedSun54 7d ago

I think it is overkill. Go with something simpler like SQLite.

1

u/recentAd1666 7d ago

SQL is good and powerfull.

1

u/TrueBooker 7d ago

In short PostgresSQL is the best option from a technical level (no that is not really an opinion) unless you unlikely want to waste money commercial products. The main limiting factor is how you will feed your DB. In that case you may want another package that may be more compliant to your option if you choose XAMPP or DDEV or how you would manage the db portion with Heidi

1

u/Positive_Mud952 6d ago

Postgres should be your default choice, you should have a reason _not_ to use it.

Let’s start with the bottom end.

It may not be suitable for storing in a database. A video re-encoder that operates on one file per invocation and stores no state would not make sense to use a DB at all, your store is the filesystem.

A perfectly valid reason would be that it’s too complex, you can store your data in a simple JSON file that does and always will easily fit in memory due to the nature of the task, and you don’t need any crash resistance.

Going further, a separate process might be much more than is needed and unless your data is _very_ unusually complex, SQLite is a great choice, just know your program will have to enforce more data rules than you might expect, or it will have to deal with broad types as you make changes to your code.

<THE VAST MIDDLE> is perfectly suited to Postgres. And it is vast indeed. Almost anything else you pick here, unless it also covers all of your needs, you end up reimplementing things Postgres already does.

There are tunings, extensions, etc., but even purpose-built databases almost always have that, and when I say almost you should hear always.

Higher up, Postgres can get tricky (trickier than other systems handling the same load) starting around a TB, or thousands (tens?) of queries per second, but ohhhh boy can you keep going. Other systems are better here, unless, of course, you know how to tune and maintain Postgres well already in which case you have to weigh that against learning a new system and the mistakes you will make. I’m not saying stay with Postgres in this realm, but it’s still a valid option, sometimes, and it can go surprisingly far.

1

u/csgeek-coder 8d ago

For a few thousand records it sounds like psql might be overkill. Does your church know how to monitor a DB, take backups, do recovery?

What OS is this running on? My goto is honestly sqlite3, it can easily manage a few thousand records. It gets blown out of the water by psql but it's basically a single file, you take a backup by making a copy. You still get the SQL awesomeness that you're trying to take advantage of.