From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pietro Pugni <pietro.pugni@gmail.com>
cc: Rick Otten <rottenwindfish@gmail.com>, pgsql-performance@postgresql.org
Subject: Re: Disk filled-up issue after a lot of inserts and drop schema
In-reply-to: <FE960B29-7786-4A97-9288-4346F48A21A7@gmail.com>
References: <AEA46136-0A29-4F3C-8966-90178EE44B4B@gmail.com>
 <CAMAYy4K6nwkqqdRcWR4cNeYvCXAH7h4WAo6vq1AkX3+MYOezsw@mail.gmail.com>
 <28460.1473864279@sss.pgh.pa.us>
 <FE960B29-7786-4A97-9288-4346F48A21A7@gmail.com>
Comments: In-reply-to Pietro Pugni <pietro.pugni@gmail.com>
	message dated "Wed, 14 Sep 2016 19:45:34 +0200"
Date: Wed, 14 Sep 2016 13:55:51 -0400
Message-ID: <16009.1473875751@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

Pietro Pugni <pietro.pugni@gmail.com> 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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance