Re: [PERFORM] Disk filled-up issue after a lot of inserts and drop schema

Log rotation was active and set to 5MB or 1 day. I don’t know if it is a bug, but Postgres was logging even if logging_collector was set to “off”. Also, that big log file wasn’t visible for me, in fact “ls” and “du” didn’t detect it. Thanks again Best regards, Pietro Pugni > Il giorno 14 set

Re: [PERFORM] Disk filled-up issue after a lot of inserts and drop schema

Pietro Pugni writes: > I’ve jsut discovered the issue.. I set "logging_collector=off” in the > previous email but didn’t comment the other log* parameters, so Postgres > was logging every single INSERT! This was caused the disk to fill up. Ah. > The strange issue

Re: [PERFORM] Disk filled-up issue after a lot of inserts and drop schema

Thank you guys. I’ve jsut discovered the issue.. I set "logging_collector=off” in the previous email but didn’t comment the other log* parameters, so Postgres was logging every single INSERT! This was caused the disk to fill up. The strange issue is that the log file didn’t exists when the disk

Re: [PERFORM] Disk filled-up issue after a lot of inserts and drop schema

Rick Otten writes: > I don't know why something still has an open file descriptor on something > you believe has been removed, but at least that explains why you are > experiencing the discrepancy between "du" and the real available space on > the disk. Yeah, the

Re: [PERFORM] Disk filled-up issue after a lot of inserts and drop schema

In Unix/Linux with many of the common file system types, if you delete a file, but a process still has it open, it will continue to "own" the disk space until that process closes the file descriptor or dies. If you try "ls" or other file system commands, you won't actually see the file there, yet

[PERFORM] Disk filled-up issue after a lot of inserts and drop schema

I’m running PostgreSQL 9.5.4 on a virtual machine for production purposes. It runs Ubuntu 16.04.1 LTS 64bit, 32GB RAM, 461GB disk space and 4 x logical CPUs. Postgres executes the following activities: - many INSERTS for ETL - a lot of read and write operations for the main OLTP application The