Re: Hard limit on WAL space used (because PANIC sucks)
От | Claudio Freire |
---|---|
Тема | Re: Hard limit on WAL space used (because PANIC sucks) |
Дата | |
Msg-id | CAGTBQpZ+X0n8SB3qSmkXXryMeCx1Ae4WvjC6Q+QCOiZONo0zgA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Hard limit on WAL space used (because PANIC sucks) (Robert Haas <robertmhaas@gmail.com>) |
Список | pgsql-hackers |
On Wed, Jun 12, 2013 at 11:55 AM, Robert Haas <robertmhaas@gmail.com> wrote: >> I hope PostgreSQL will provide a reliable archiving facility that is ready >> to use. > > +1. I think we should have a way to set an archive DIRECTORY, rather > than an archive command. And if you set it, then PostgreSQL should > just do all of that stuff correctly, without any help from the user. > Of course, some users will want to archive to a remote machine via ssh > or rsync or what-have-you, and those users will need to provide their > own tools. But it's got to be pretty common to archive to a local > path that happens to be a remote mount, or to a local directory whose > contents are subsequently copied off by a batch job. Making that work > nicely with near-zero configuration would be a significant advance. That, or provide a standard archive command that takes the directory as argument? I bet we have tons of those available among us users...
В списке pgsql-hackers по дате отправления: