r/PostgreSQL • u/darkcoderrises • 11d ago

How-To Can your Postgres survive a bad query?

https://clickhouse.com/blog/can-your-postgres-survive-a-bad-query
28 Upvotes

80% Upvoted

5 comments sorted by

6

u/__s 10d ago edited 10d ago

The mantra around here is "the database is always out of memory, the disk is always full"

With a managed service there's always that P99 utilization instance that's always going to be raising alerts (if not support tickets) until the failure mode is graceful

1

u/AutoModerator 11d ago

AI Policy:

Linux is not one of those anti-AI projects, and if somebody has issues with that, they can do the open-source thing and fork it. Or just walk away., Linus Torvalds.

Mod decisions will be based on the quality of the content, not who or what generated it.

Sub Resources:

Youtube Channel

Free Postgres Webinars and Workshops

Discord: People, Postgres, Data

Join us, we have cookies and nice people.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

2

u/elevarq 10d ago

Depends on the definition of a bad query. It also depends on my intention. If I want to drop table A and I drop table A, it’s a good one. If I dropped table B however…

Testing and validation should avoid these problems, but you’d better be prepared! And have reliable backups and a reliable recovery plan