Not sure exactly what happened but Postgresql flooded all the available SSD
space and obviously crashed. It has written a lot of data in the pg_wal
folder. Most likely it was caused by replication. The postgresql instance
that crashed was a subscriber and publisher at the same time. Even so, it
was
On 6 November 2023 12:11:31 CET, Gabriel Dodan wrote:
>Not sure exactly what happened but Postgresql flooded all the available SSD
>space and obviously crashed. It has written a lot of data in the pg_wal
>folder. Most likely it was caused by replication. The postgresql instance
>that crashed wa
On Mon, Nov 06, 2023 at 01:11:31PM +0200, Gabriel Dodan wrote:
> Not sure exactly what happened but Postgresql flooded all the available SSD
> space and obviously crashed. It has written a lot of data in the pg_wal
> folder. Most likely it was caused by replication. The postgresql instance
> that c
Dear all,
I’m reasonably experienced with Postgres with simple (single, „rebuild and
restore“) requirements, but would need some hints on what to look for in a more
complex situation - deploying Postgres as the backend for a (virtual)
appliance.
This appliance can scale horizontally from a si
On Thu, Nov 2, 2023 at 4:13 AM Avi Weinberg wrote:
> Hi experts,
>
>
>
> I'm using Patroni Postgres installation and noticed that twice already
> postgres crashed due to out of memory. I'm using logical replication with
> around 30-40 active subscribers on this machine. The machine has 128GB bu
