Re: 7.1 startup recovery failure
От | Rod Taylor |
---|---|
Тема | Re: 7.1 startup recovery failure |
Дата | |
Msg-id | 015f01c0d1ec$80734960$2205010a@jester обсуждение исходный текст |
Ответ на | 7.1 startup recovery failure (Hiroshi Inoue <Inoue@tpf.co.jp>) |
Ответы |
Re: 7.1 startup recovery failure
|
Список | pgsql-hackers |
Corrupted or not, after a crash take a snapshot of the data tree before firing it back up again. Doesn't take that much time (especially with a netapp filer) and it allows for a virtually unlimited number of attempts to solve the trouble or debug. -- Rod Taylor BarChord Entertainment Inc. ----- Original Message ----- From: "Hiroshi Inoue" <Inoue@tpf.co.jp> To: "Vadim Mikheev" <vmikheev@sectorbase.com> Cc: "pgsql-hackers" <pgsql-hackers@postgresql.org> Sent: Monday, April 30, 2001 11:02 PM Subject: Re: [HACKERS] 7.1 startup recovery failure > Vadim Mikheev wrote: > > > > > There's a report of startup recovery failure in Japan. > > > Redo done but ... > > > Unfortunately I have no time today. > > > > Please ask to start up with wal_debug = 1... > > > > Isn't it very difficult for dbas to leave the > corrupted database as it is ? > ISTM we could hardly expect to get the log with > wal_debug = 1 unless we automatically force the > log in case of recovery failures. > > regards, > Hiroshi Inoue > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://www.postgresql.org/search.mpl >
В списке pgsql-hackers по дате отправления: