CheckEmoji Community · the emoji forum
🏠 Home 🆕 What's new ❓ Unanswered 🔥 Popular 📡 RSS Members 👥 0 online log in · register
Home › IT › Hardware › Desktops › PostgreSQL: Best practices and troubleshooting?

PostgreSQL: Best practices and troubleshooting?

Started by neonviper8 · · 👁 5 views · 3 replies

📡 Subscribe to replies

Participants neonviper8analogtiger19Michael Jackson10William Richardson12
neonviper8 neonviper8 NewcomerOP
6 messages
joined Oct 2015
#1 ·
I’ve been spending a little bit of my afternoon attempting to clear out some much-needed breathing room on my hard drive... and I just stumbled upon the fact that this particular folder is sitting at a staggering 105 GB
😲

Is that actually considered normal behavior for a system like this?

I can't quite wrap my head around where on earth all that space went.
analogtiger19 analogtiger19 Active Member
134 messages
joined Dec 2016
#2 ·
I mean, you surely know what's actually sitting inside your database, right? 🤔

Whose computer are you even hacking away at? 😬
Michael Jackson10 Michael Jackson10 Active Member
140 messages
joined Feb 2023
#3 ·
Honestly, it feels like you’re poking around at stuff you don't quite grasp yet, just based on how you asked that..
A database can bloat for all sorts of reasons: where the backups are sitting, the logs, those snapshots—basically everything that isn't directly under the engine itself. That’s more of an admin's headache..
If we're talking about a corporate environment, you really want someone who knows their way around touching those files. But if this is just some home setup you threw together for fun, why even bother?
William Richardson12 William Richardson12 Regular
301 messages
joined Aug 2014
#4 ·
Don't go messing around with your computer if you don't know how to use Google 🤦 at least learn that before you start anything... otherwise my local "experts" end up getting pissed off.

You must log in or register to reply here.

Log in Register

🔗 Similar threads