Re: BUG #4879: bgwriter fails to fsync the file in recovery mode
От | Fujii Masao |
---|---|
Тема | Re: BUG #4879: bgwriter fails to fsync the file in recovery mode |
Дата | |
Msg-id | 3f0b79eb0906251856p72777b81gc8c37b8ffe283d42@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #4879: bgwriter fails to fsync the file in recovery mode (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: BUG #4879: bgwriter fails to fsync the file in recovery
mode
Re: BUG #4879: bgwriter fails to fsync the file in recovery mode |
Список | pgsql-bugs |
Hi, Thank you for addressing the problem! On Fri, Jun 26, 2009 at 7:14 AM, Heikki Linnakangas<heikki.linnakangas@enterprisedb.com> wrote: > We certainly update it an order of magnitude more often than before, but > I don't think that's an issue. We're talking about archive recovery > here. It's not like in normal operation where a corrupt pg_control file > means that you lose your data. It will stop the server from starting up, > but there's many other files that can be corrupt in a way that causes > recovery to fail or stop too early. Frequent updating of pg_control causes the significant performance degradation of archive recovery. I think that this is an issue to be fixed. The warm-standby users (including me) care about the performance of the standby server, because that affects the failover time, for example. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
В списке pgsql-bugs по дате отправления: