We have in our local network a server with a Postgres-Installation. Now, as some big inserts (needed days) were running, others had problems connecting via pgadmin. After opening the Server in pgadmin (that would showing the tables in the overview) pgadmin was trying and trying, without progress. As I understand that the inserts can slow down access to the same database, it shouldn't prevent them at all, am I right? So what's going wrong here?
If I had to guess, I'd say the server is running out of RAM and swapping heavily, so it's not servicing requests properly. It may also explain why the inserts are taking so long.
Can you ssh into the server?
Does
top
show significant swap use?There isn't really enough info in the question to really say, beyond pointing you in that direction.
Most likely the insert will actually slow down the connection significally.
what you could try : renice and ionice the backend pid with the insert statement. Depending how you start the sql you might be able to directly use the "script" with lower IO prio.