Re: basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe?

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe?
Дата
Msg-id 20150122194345.GF1663@alvh.no-ip.org
обсуждение исходный текст
Ответ на Re: basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe?  (Andres Freund <andres@2ndquadrant.com>)
Ответы Re: basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Список pgsql-hackers
Andres Freund wrote:

> 2) Make movedb() (and possibly created(), not sure yet) use proper WAL
>    logging and log the whole copied data. I think this is the right long
>    term fix and would end up being much more reliable. But it either
>    requires some uglyness during redo (creating nonexistant database
>    directories on the fly during redo) or new wal records.
> 
>    Doable, but probably too large/invasive to backpatch.

Not to mention the extra WAL traffic ...

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



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

Предыдущее
От: Jim Nasby
Дата:
Сообщение: Re: Proposal: knowing detail of config files via SQL
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: proposal: plpgsql - Assert statement