Re: skipping pg_log in basebackup (was Re: pg_basebackup and pg_stat_tmp directory)

Поиск
Список
Период
Сортировка
От Joshua D. Drake
Тема Re: skipping pg_log in basebackup (was Re: pg_basebackup and pg_stat_tmp directory)
Дата
Msg-id 5578701A.7070507@commandprompt.com
обсуждение исходный текст
Ответ на Re: skipping pg_log in basebackup (was Re: pg_basebackup and pg_stat_tmp directory)  (Andres Freund <andres@anarazel.de>)
Ответы Re: skipping pg_log in basebackup (was Re: pg_basebackup and pg_stat_tmp directory)
Список pgsql-hackers
On 06/10/2015 10:01 AM, Andres Freund wrote:
>
> On 2015-06-10 09:57:17 -0700, Jeff Janes wrote:
>> Mine goal isn't that.  My goal is to have a consistent backup without
>> having to shut down the server to take a cold one, or having to manually
>> juggle the pg_start_backup, etc. commands.
>
> A basebackup won't necessarily give you a consistent log though...

I am -1 on this idea. It just doesn't seem to make sense. There are too 
many variables where it won't work or won't be relevant.

JD


-- 
Command Prompt, Inc. - http://www.commandprompt.com/  503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robbie Harwood
Дата:
Сообщение: Re: Postgres GSSAPI Encryption
Следующее
От: Robert Haas
Дата:
Сообщение: Re: s_lock() seems too aggressive for machines with many sockets