Re: pgsql: pg_stop_backup was
От | Bruce Momjian |
---|---|
Тема | Re: pgsql: pg_stop_backup was |
Дата | |
Msg-id | 200611142240.kAEMec002035@momjian.us обсуждение исходный текст |
Ответ на | Re: pgsql: pg_stop_backup was callingXLogArchiveNotify() twice for the ("Simon Riggs" <simon@2ndquadrant.com>) |
Ответы |
Re: pgsql: pg_stop_backup wascallingXLogArchiveNotify() twice for the
|
Список | pgsql-committers |
Simon Riggs wrote: > On Thu, 2006-06-22 at 17:43 -0300, Tom Lane wrote: > > Log Message: > > ----------- > > pg_stop_backup was calling XLogArchiveNotify() twice for the newly created > > backup history file. Bug introduced by the 8.1 change to make pg_stop_backup > > delete older history files. Per report from Masao Fujii. > > > > Tags: > > ---- > > REL8_1_STABLE > > > > Modified Files: > > -------------- > > pgsql/src/backend/access/transam: > > xlog.c (r1.222.2.3 -> r1.222.2.4) > > (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c.diff?r1=1.222.2.3&r2=1.222.2.4) > > > This doesn't seem to be mentioned in the 8.1.5 release notes, so people > would not be aware they should upgrade to fix this. We don't mention every fix for every minor release. People should upgrade anyway, as we state in the FAQ. Is there a reason this item was significant? -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
В списке pgsql-committers по дате отправления: