Re: PITR Dead horse?
От | Greg Stark |
---|---|
Тема | Re: PITR Dead horse? |
Дата | |
Msg-id | 87wu3fpoyd.fsf@stark.xeocode.com обсуждение исходный текст |
Ответ на | Re: PITR Dead horse? ("scott.marlowe" <scott.marlowe@ihs.com>) |
Список | pgsql-hackers |
"scott.marlowe" <scott.marlowe@ihs.com> writes: > but I'm not sure you can test that without power off tests... Well the approach that's been taken manually on the list is to look at the timing results and conclude they're just physically impossible. Doing this automatically could be interesting. If the tool were given a partition to act on directly it would be able to intentionally write to blocks in reverse order doing an fsync between each block and testing whether the bandwidth is low enough to conclude a full rotation between each write had been completed. Doing the same on the filesystem would be less reliable but might also be an interesting test since the OS might make fsync lie directly, or might have some additional intelligence in the filesystem that forces the drive to sync to the platters before fsync returns. -- greg
В списке pgsql-hackers по дате отправления: