Re: BUG #15785: create slave through archive log replication

Em seg, 29 de abr de 2019 às 05:44, PG Bug reporting form
<noreply@postgresql.org> escreveu:
>
> I have one master and slave1 and  i am creating one more slave through
> archive log , but is showing below error after 4 hr replication.
>
This is not a bug. Use  pgsql-general ML instead.

> cp: cannot stat
> /var/lib/pgsql/11/data/pg_log_archive/0000000100002C2F0000000A No such file
> or directory
> 2019-04-29 11:29:43.518 IST [852] LOG:  started streaming WAL from primary
> at 2C2F 28000000 on timeline 1
> 2019-04-29 11 2943.518 IST [852] FATAL   could not receive data from WAL
> stream: ERROR:  requested WAL segment 0000000100002C2F0000000A has already
> been removed
>
Master and slave are in the same host?

>
> Recovery.conf:
>
> standby_mode = 'on'
> primary_conninfo = 'user=postgres passfile=''/var/lib/pgsql/.pgpass''
> host=XXX.XXX.X.XX port=5432 sslmode=prefer sslcompression=0
> krbsrvname=postgres target_session_attrs=any'
> restore_command = 'cp /var/lib/pgsql/11/data/pg_log_archive/%f "%p"'
>
... if master and slave aren't in the same host, restore_command must
grab archives directly from master (or archive directly in slave or
even in another host) such as:

restore_command = 'scp
postgres@myhost:/var/lib/pgsql/11/data/pg_log_archive/%f %p'

In this case, user postgres in myhost must access master without password.


--
   Euler Taveira                                   Timbira -
http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento