Re: base backup client as auxiliary backend process
От | Euler Taveira |
---|---|
Тема | Re: base backup client as auxiliary backend process |
Дата | |
Msg-id | CAHE3wghQKiiW5oAN-D6CKjqfhCjX9sL5=T=ynSgQCYyCV=d4mA@mail.gmail.com обсуждение исходный текст |
Ответ на | base backup client as auxiliary backend process (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>) |
Список | pgsql-hackers |
Em sáb, 29 de jun de 2019 às 17:05, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> escreveu: > > Setting up a standby instance is still quite complicated. You need to > run pg_basebackup with all the right options. You need to make sure > Attached is a very hackish patch to implement this. It works like this: > > # (assuming you have a primary already running somewhere) > initdb -D data2 --minimal > $EDITOR data2/postgresql.conf # set primary_conninfo > pg_ctl -D data2 start > Great! The main complaints about pg_basebackup usage in TB clusters are: (a) it can't be restarted and (b) it can't be parallelized. AFAICS your proposal doesn't solve them. It would be nice if it can be solved in future releases (using rsync or another in-house tool is as fragile as using pg_basebackup). -- Euler Taveira Timbira - http://www.timbira.com.br/ PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
В списке pgsql-hackers по дате отправления: