ql.org
*Subject:* Re: [GENERAL] Interrupted streaming replication
As long as you have 00010089002C and the subsequent WALs in
your archive directory, then you should
be able to simply scp them to you second slave's pg_xlog directory.
On Mon, Dec 7, 2015 at 8:50 AM, Ton
Melvin Davidson wrote:
> As long as you have 00010089002C and the subsequent WALs in your
> archive directory, then you should
> be able to simply scp them to you second slave's pg_xlog directory.
Nice idea ;-)
wasn't sure if that works, but yes, nice.
Andreas
--
Really, I'm not
@postgresql.org
Subject: Re: [GENERAL] Interrupted streaming replication
As long as you have 00010089002C and the subsequent WALs in your
archive directory, then you should
be able to simply scp them to you second slave's pg_xlog directory.
On Mon, Dec 7, 2015 at 8:50 AM, Tony N
On 12/07/2015 05:50 AM, Tony Nelson wrote:
-Original Message-
Tony Nelson wrote:
2015-12-07 08:24:50 EST FATAL: requested WAL segment
00010089002C has already been removed
Can I simply copy the file from my archive directory back to the WAL
directory?
I'm afraid th
As long as you have 00010089002C and the subsequent WALs in
your archive directory, then you should
be able to simply scp them to you second slave's pg_xlog directory.
On Mon, Dec 7, 2015 at 8:50 AM, Tony Nelson wrote:
>
>
> > -Original Message-
> > Tony Nelson wrote:
> >
>
> -Original Message-
> Tony Nelson wrote:
>
> > 2015-12-07 08:24:50 EST FATAL: requested WAL segment
> > 00010089002C has already been removed
> >
> >
> >
> > Can I simply copy the file from my archive directory back to the WAL
> directory?
>
> I'm afraid that won't work, be
Tony Nelson wrote:
> 2015-12-07 08:24:50 EST FATAL: requested WAL segment 00010089002C
> has already been removed
>
>
>
> Can I simply copy the file from my archive directory back to the WAL
> directory?
I'm afraid that won't work, because of the master knows nothing about
this
Hi all,
I have a small problem of my own making. I have a simple streaming replication
setup, one master and two slaves. One slave is in the same rack as the master,
the other is across a "slow" link in another server room.
Last night I executed some updates that caused a lot of changes. The
