Yeah it is latest.
I am using Postgres 9.6.
Thanks!
Sudhakaran
On Tue, 15 Jun 2021 at 10:42 PM, Mateusz Henicz
wrote:
> Do you have "recovery_target_timeline=latest" configured in your
> recovery.conf or postgresql.conf? Depending on the version you are using,
> up to 11 recovery.conf and
At Tue, 15 Jun 2021 07:05:07 -0700 (MST), "email2ssk...@gmail.com"
wrote in
> Even I have this problem when I had to recover the database failed
> switchover.
> This is error is new primary server.
>
> < 2021-06-15 16:05:02.480 CEST > ERROR: requested starting point
> AF/7D00 on timeline
Do you have "recovery_target_timeline=latest" configured in your
recovery.conf or postgresql.conf? Depending on the version you are using,
up to 11 recovery.conf and postgresql.conf 12+.
Cheers,
Mateusz
wt., 15 cze 2021, 22:05 użytkownik email2ssk...@gmail.com <
email2ssk...@gmail.com> napisał:
Even I have this problem when I had to recover the database failed
switchover.
This is error is new primary server.
< 2021-06-15 16:05:02.480 CEST > ERROR: requested starting point
AF/7D00 on timeline 1 is not in this server's history
< 2021-06-15 16:05:02.480 CEST > DETAIL: This server's
Hello,
I've created synchronous replication between Primary and Secondary server and
put pacemaker + PAF over. Client is doing some stress tests (switching nodes,
disabling particular node, etc) and it's second time when this kind of problem
occoures :
2020-12-18 14:03:46.658 CET [unknown]
On Mon, 23 Sep 2019, 00:46 Shital A, wrote:
>
> Hello,
>
> We have setup active-passive cluster using streaming replication on Rhe
> 7.5. We are testing pacemaker for automated failover.
> We are seeing below issues with the setup :
>
> 1. When a failoveris triggered when data is being added to
Hello,
We have setup active-passive cluster using streaming replication on Rhe
7.5. We are testing pacemaker for automated failover.
We are seeing below issues with the setup :
1. When a failoveris triggered when data is being added to the primary by
killing primary (killall -9 postgres), the
On 28/9/18 1:50 μ.μ., bhargav kamineni wrote:
Ee are using 9.5 version, slot option -s is not available ,can I go with -X
stream option ?
-S is intended when you plan to use the backup as a hot standby, when you must
use the same replication slot.
If you plan to use the backup as a stand
Ee are using 9.5 version, slot option -s is not available ,can I go with -X
stream option ?
On Fri 28 Sep, 2018, 12:01 PM Laurenz Albe,
wrote:
> bhargav kamineni wrote:
> > Hi Team,
> >
> > I have configured replication using slot ,But it failed by throwing the
> > ERROR pg_basebackup: could
bhargav kamineni wrote:
> Hi Team,
>
> I have configured replication using slot ,But it failed by throwing the
> ERROR pg_basebackup: could not get transaction log end position from server:
> ERROR: requested WAL segment 00012C9D0085 has already been
> removed ,
> which is
On 28/9/18 9:00 π.μ., bhargav kamineni wrote:
Hi Team,
I have configured replication using slot ,But it failed by throwing the ERROR /pg_basebackup: could not get transaction log end position from server: ERROR: requested WAL segment
00012C9D0085 has already been removed /, which
Hi Team,
I have configured replication using slot ,But it failed by throwing the
ERROR *pg_basebackup: could not get transaction log end position from
server: ERROR: requested WAL segment 00012C9D0085 has already
been removed *, which is unexpected because i have created the slot
12 matches
Mail list logo
