Re: pause recovery if pitr target not reached

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Leif Gunnar Erlandsen <leif(at)lako(dot)no>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pause recovery if pitr target not reached
Date: 2019-11-22 10:50:49
Message-ID: 3c37bc5a-0992-26df-c8bd-6f50ace3adaa@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-11-21 13:50, Leif Gunnar Erlandsen wrote:
> Pausing was choosen in the patch as pause was the expected behaivior if target was reached.

Pausing is the expect behavior when the target is reached because that
is the default setting of recovery_target_action. Your patch does not
take recovery_target_action into account.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2019-11-22 10:56:34 Re: logical decoding : exceeded maxAllocatedDescs for .spill files
Previous Message Jinbao Chen 2019-11-22 10:50:43 Re: Planner chose a much slower plan in hashjoin, using a large table as the inner table.