From: Pietro Pugni <pietro.pugni@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Rick Otten <rottenwindfish@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Disk filled-up issue after a lot of inserts and drop schema
Date: Wed, 14 Sep 2016 20:00:59 +0200
Message-ID: <F4AC0CD0-0BCA-493F-87B0-E6AD169B4EB5@gmail.com> (raw)
In-Reply-To: <16009.1473875751@sss.pgh.pa.us>
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>
<16009.1473875751@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
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@sss.pgh.pa.us> ha scritto:
>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pietro.pugni@gmail.com, tgl@sss.pgh.pa.us, rottenwindfish@gmail.com
Subject: Re: Disk filled-up issue after a lot of inserts and drop schema
In-Reply-To: <F4AC0CD0-0BCA-493F-87B0-E6AD169B4EB5@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox