Re: remove pg_standby?
От | Magnus Hagander |
---|---|
Тема | Re: remove pg_standby? |
Дата | |
Msg-id | CABUevEz-ZG45mQvnSPOKBz==N9T-RTgS+QGit4EuKtQUM1pi-Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: remove pg_standby? (Fujii Masao <masao.fujii@gmail.com>) |
Ответы |
Re: remove pg_standby?
|
Список | pgsql-hackers |
<p dir="ltr"><br /> On Nov 10, 2014 6:16 PM, "Fujii Masao" <<a href="mailto:masao.fujii@gmail.com">masao.fujii@gmail.com</a>>wrote:<br /> ><br /> > On Wed, Nov 5, 2014 at 6:36AM, Peter Eisentraut <<a href="mailto:peter_e@gmx.net">peter_e@gmx.net</a>> wrote:<br /> > > While we'retalking about removing old things, is there any use left for<br /> > > pg_standby?<br /> ><br /> > -1 forremoving it. There is still the case where I'd like to use log-shipping<br /> > rather than replication. For example,it's the case where I need to<br /> > compress WAL files before streaming them via very thin network.<br /> >We can set up log-shipping using standby_mode and without using<br /> > pg_standby, but it keeps emitting the failureof restore_command while<br /> > while there is no WAL activity, and which is bothersome. So I still need<br />> pg_standby for log-shipping.<p dir="ltr">I didn't realize that part, but maybe we should fix that instead of keepingpg_standby around? <p dir="ltr">(BTW, you can use streaming with compression as well using ssl of course, but it won'tget quite the same levels due to smaller block sizes. And there are certainly still reasons for file based standbysso we should definitely not remove that) <p dir="ltr">/Magnus <br />
В списке pgsql-hackers по дате отправления: