Re: fsync-pgdata-on-recovery tries to write to more files than previously
От | Alvaro Herrera |
---|---|
Тема | Re: fsync-pgdata-on-recovery tries to write to more files than previously |
Дата | |
Msg-id | 20150525200614.GP5885@postgresql.org обсуждение исходный текст |
Ответ на | Re: fsync-pgdata-on-recovery tries to write to more files than previously (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: fsync-pgdata-on-recovery tries to write to more files than previously
|
Список | pgsql-hackers |
Tom Lane wrote: > Stephen Frost <sfrost@snowman.net> writes: > > I've not followed this thread all that closely, but I do tend to agree > > with the idea of "only try to mess with files that are *clearly* ours to > > mess with." > > Well, that opens us to errors of omission, ie failing to fsync things we > should have. Maybe that's an okay risk, but personally I'd judge that > "fsync everything and ignore (some?) errors" is probably a more robust > approach over time. How is it possible to make errors of omission? The list of directories in initdb is the complete set of directories that are created for a newly-initdb'd database, no? Surely there can't be a database that contains vital directories that are not created there? See "subdirs" static in initdb.c. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: