Re: Forcing WAL switch
От | Walker, Jed S |
---|---|
Тема | Re: Forcing WAL switch |
Дата | |
Msg-id | F7638DABBEBB4A4CB70616DE2B19E6B8067279@COENGEXCMB01.cable.comcast.com обсуждение исходный текст |
Ответ на | Forcing WAL switch ("Walker, Jed S" <Jed_Walker@cable.comcast.com>) |
Ответы |
Re: Forcing WAL switch
|
Список | pgsql-novice |
To have a good hot backup. It is worthless if I don't have the log that was being written to at the time the backup was occurring correct? If I'm wrong please explain. -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Thursday, August 11, 2005 9:04 AM To: Walker, Jed S Cc: pgsql-novice@postgresql.org Subject: Re: [NOVICE] Forcing WAL switch "Walker, Jed S" <Jed_Walker@cable.comcast.com> writes: > I can't find a way to force a WAL to switch other than just generating > a lot of changes in the database. I'd like to be able to switch to the > next WAL before a hot backup, and then switch out one after the hot > backup. What's the point? regards, tom lane
В списке pgsql-novice по дате отправления: