Hello, Magnus-san, Itagaki-san
From: "Magnus Hagander" <[EMAIL PROTECTED]>
>> I think many people can benefit from Itagaki-san's proposal, and
>> NO_BUFFERING should be default. Isn't it very rare that disks with
>> sector size larger than 8KB are used?
> Definitly very rare.
>> Providing a way (such as
>> wal_sync_method) to avoid NO_BUFFERING is sufficient for people in
>> rare environments. Or, by determining the sector size with
>> GetDiskFreeSpaceEx(), we could auto-switch to not using
>> when the sector size is larger than 8KB.
> I think the second one is better.
Thank you for agreeing. Then, I hope Itagaki-san's patch will be
accepted when the following treatments are added to the patch and some
performance report is delivered.
1. On Windows, O_DIRECT (and O_SYNC?) is default for WAL.
2. Auto-switch to not using O_DIRECT if the sector size is larger than
8KB when the server starts.
> A quick google shows some inconclusive results :-)BUt look at for
> This seems to indicate that *Windows* supports sector sizes >4K, but
> Server doesn't. But again, it could be a mixup between cluster and
> sector size...
This is interesting. I've never seen systems with a sector size
larger than 4KB, too. On IBM zSeries (which is a mainframe running
Linux), DASD (direct attached storage device) is usually used as a
hard disk. The sector size of DASD is 4KB. So, the current
implementation of PostgreSQL which assumes 8KB sector size is
Delivering an intuitive error message like SQL Server is one way when
PostgreSQL encounters devices with a larger sector size than is
supported. However, as you say, auto-switching to not using
NO_BUFFERING is kinder to users.
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings