RE: New statistics for tuning WAL buffer size - Mailing list pgsql-hackers

From tsunakawa.takay@fujitsu.com
Subject RE: New statistics for tuning WAL buffer size
Date
Msg-id TYAPR01MB2990A96CDC6D7FB133CF1BA4FE5B0@TYAPR01MB2990.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: New statistics for tuning WAL buffer size  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-hackers
From: Fujii Masao <masao.fujii@oss.nttdata.com>
> I agree to expose the number of WAL write caused by full of WAL buffers.
> It's helpful when tuning wal_buffers size. Haribabu separated that number
> into two fields in his patch; one is the number of WAL write by backend,
> and another is by background processes and workers. But I'm not sure
> how useful such separation is. I'm ok with just one field for that number.

I agree with you.  I don't think we need to separate the numbers for foreground processes and background ones.  WAL
bufferis a single resource.  So "Writes due to full WAL buffer are happening.  We may be able to boost performance by
increasingwal_buffers" would be enough.
 


Regards
Takayuki Tsunakawa


pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Creating foreign key on partitioned table is too slow
Next
From: "tsunakawa.takay@fujitsu.com"
Date:
Subject: RE: New statistics for tuning WAL buffer size