From: | Christophe Pettus <xof(at)thebuild(dot)com> |
---|---|
To: | sit7602(at)gmail(dot)com, PostgreSQL Bug List <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #18724: High data disk utilization during log writing |
Date: | 2024-11-25 14:47:23 |
Message-ID: | 9B2DED60-3C47-48A2-9F59-392749D820F1@thebuild.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> On Nov 25, 2024, at 04:26, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
> The lsof utility did not help in investigating this problem, as did
> restarting the server
> Setting log_min_duration_statement = -1 shows a significant decrease in the
> load on the data disk
> So I can't assume why data disk (/dev/vdb1 /data) utilized up to 60-80%
> while statements are logged to separate block device (/dev/vdc1
> /var/log/postgresql) and need some help to get off the ground
The question seems to answer itself here: You are logging every statement to the text logs, and it is very likely that the lines in the text log are larger than the actual data for that statement being written to the data disk. It can be very expensive to log every statement, especially when you have a significant query load (which you do here).
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-11-25 15:07:31 | Re: BUG #18722: Processing arrays with plpgsql raises errors |
Previous Message | PG Bug reporting form | 2024-11-25 12:26:52 | BUG #18724: High data disk utilization during log writing |