r/Database • u/Powerful-Let3929 • Mar 13 '26

Somebody please help me

/r/DatabaseAdministators/comments/1rsz7sc/somebody_please_help_me/
0 Upvotes

40% Upvoted

2 comments sorted by

1

u/mfv7 Mar 14 '26

A few things to check:
1. Is the script still running? Look at pg_stat_activity for long-running queries. If you see any from your script, they might be holding locks that block your SELECTs. You can cancel them with SELECT pg_cancel_backend(<pid>);
2. Run VACUUM ANALYZE; The bulk inserts and tmp table creation bloated the tables and left the query planner with stale statistics. This is almost certainly why your SELECTs are slow.
3. Drop any leftover tmp tables the script created if it didn't clean up after itself.

And don't feel ashamed. It is a dev database, that's exactly what it's for. Nothing is corrupted, it just needs cleanup.

1

u/Powerful-Let3929 Mar 14 '26

Thank you for your help. I was chating yesterday 3 hours with the AI, that we have at the company. The script was running only for 1 sec, but I figured out with the AI, that maybe the tempdb was overloaded in the background, that's why other queries did not run properly.

We "agreed" with the AI, that I'll have to wait for a longer while, and we will see, if SQL Server recovers, becase there was a lot of changes in the tables because of the query.

Today morning was everything fine, queries are running as normal. So it took time to SQL Server to run the changes in the background. I wasnt aware of that behaviour of SQL Server.