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 2016, alle ore 19:55, Tom Lane <tgl@xxxxxxxxxxxxx> ha scritto: > > Pietro Pugni <pietro.pugni@xxxxxxxxx> 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 is that the log file didn’t exists when the disk filled up. I personally looked for it but it wasn’t where it should have been ( /var/log/postgesql/ ), so I can’t exactly confirm that the issue was the log file getting bigger and bigger. > > Seems like the log file must have gotten unlinked while still active, > or at least, *something* had an open reference to it. It's hard to > speculate about the cause for that without more info about how you've got > the logging set up. (Are you using the log collector? Are you rotating > logs?) But I seriously doubt it represents a Postgres bug. Unlike the > situation with data files, it's very hard to see how PG could be holding > onto a reference to an unused log file. It only ever writes to one log > file at a time. > > regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
