Re: Remove fsync ON/OFF as a visible option?
От | Jim Nasby |
---|---|
Тема | Re: Remove fsync ON/OFF as a visible option? |
Дата | |
Msg-id | 550CA939.1090705@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: Remove fsync ON/OFF as a visible option? (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: Remove fsync ON/OFF as a visible option?
|
Список | pgsql-hackers |
On 3/20/15 2:49 PM, Stephen Frost wrote: > How about a big warning around fsync and make it more indepenent from > the options around it? +1, and the same for full_page_writes and wal_sync_method. I think that's the best we can do at this point. As for why; Postgres already has a big reputation for being "hard to use" and "hard to setup". Leaving footguns laying around that could easily be warned about is part of the reason for that reputation. Reality is that there are a lot of people using Postgres that are nowhere close to being DBAs and making it easy for them to munch their data on accident doesn't help anyone. -- Jim Nasby, Data Architect, Blue Treble Consulting Data in Trouble? Get it in Treble! http://BlueTreble.com
В списке pgsql-hackers по дате отправления: