Re: BUG #17577: pg_ctl promote is not preemptive in archive recovery

From: Daniel Farina <daniel(at)fdr(dot)io>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17577: pg_ctl promote is not preemptive in archive recovery
Date: 2022-08-05 20:01:19
Message-ID: CACN56+Pe0Nitnn-+d9=sfYG_1S_vrsRZrsr4ZNWQhbf25auHaw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Aug 5, 2022 at 12:21 PM David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> On Fri, Aug 5, 2022 at 12:10 PM PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
>>
>> The following bug has been logged on the website:
>>
>> Bug reference: 17577
>> Logged by: Daniel Farina
>> Email address: daniel(at)fdr(dot)io
>> PostgreSQL version: 14.4
>> Operating system: AlmaLinux 8.6
>> Description:
>>
>>
>> 5) try to run pg_ctl promote while the server is in archive restore
>> 6) it will block until timeout, and not promote until restore_command exits
>> abnormally
>>
>
> On what basis are you considering this a bug? Or, IOW, what do you expect to happen? It doesn't seem possible for the promotion to actually happen as the server knows additional WAL must exist that it hasn't yet restored since all attempts to restore WAL have succeeded.

pg_ctl promote should have consistent behavior regardless of WAL
transport. If I (or a computer program of mine) is issuing pg_ctl
promote, I mean for it to happen now, that's how it happens with
streaming, and in the case of streaming, the amount of WAL that can
eventually come into existence is practically unbounded.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2022-08-05 21:16:57 BUG #17578: undetected (on one side) deadlock with reindex CONCURRENTLY partitioned index vs drop index
Previous Message David G. Johnston 2022-08-05 19:21:01 Re: BUG #17577: pg_ctl promote is not preemptive in archive recovery