Re: initdb and fsync
| От | Robert Haas |
|---|---|
| Тема | Re: initdb and fsync |
| Дата | |
| Msg-id | CA+TgmoYqLpagU3GSvvxbHPs9UhQq4QSYCvdD=qj6UiAyPFJTEw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: initdb and fsync (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: initdb and fsync
|
| Список | pgsql-hackers |
On Fri, Mar 16, 2012 at 6:25 AM, Andres Freund <andres@anarazel.de> wrote: >> > How are the results with sync_file_range(fd, 0, 0, >> > SYNC_FILE_RANGE_WRITE)? >> That is much faster than using fadvise. It goes down to ~2s. > >> Unfortunately, that's non-portable. Any other ideas? 6.5s a little on >> the annoying side (and causes some disconcerting sounds to come from my >> disk), especially when we _know_ it can be done in 2s. > Its not like posix_fadvise is actually portable. So I personally don't see a > problem with that, but... Well, sync_file_range only works on Linux, and will probably never work anywhere else. posix_fadvise() at least has a chance of being supported on other platforms, being a standard and all that. Though I see that my Mac has neither. :-( -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: