# Postgres problem... again! **URL:** \ **Category:** Self-hosting\ **Created:** [October 29, 2021, 5:26pm UTC](https://meta.discourse.org/t/postgres-problem-again/207568 "2021-10-29T17:26:58Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Wanderer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/wanderer/32/233165_2.png) [@Wanderer](https://meta.discourse.org/u/Wanderer)\ **Post date:** [October 29, 2021, 7:24pm UTC](https://meta.discourse.org/t/postgres-problem-again/207568/3 "2021-10-29T19:24:55Z")
> [@Falco](#): > > No it’s not a mistake. This file is in the volume that gets mounted in the container, so it has different paths depending on the point of view, aka inside the container vs outside the container. But I find this “nginx.http.sock” created on “shared/standalone” in the host file system, too. Initially pink, as a socket, but after a while, maybe a stop, it becomes blue, as a directory, and container refuses to start stuck on trying deleting a socket… become a directory. > [@Falco](#): > > This happens when the container is not stopped properly. PostgreSQL needs some time to properly shutdown, and we do that when you stop with our launcher command. However, if your instance if of a big enough size, or there are too many running transactions the database may struggle to stop properly in the deadline it receives. So, what can we do in order to fix it? Until now, I’m just experimenting, but should I go online with some hundred people connected and hundred thousands post, will I risk to loose everything just because Postgres doesn’t manage abruptly interruption? It will be something to do in order to fix a damaged database. Can Discourse run on external Postgres, something that we can manage if Discourse container doesn’t start? In short, in case of “PANIC” or “FATAL”, there should be some fix… --- _[View the full topic](https://meta.discourse.org/t/postgres-problem-again/207568)._