RE: BUG: Former primary node might stuck when started as a standby - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: BUG: Former primary node might stuck when started as a standby
Date
Msg-id OS9PR01MB121491FE3BD5D9D7341B83537F57FA@OS9PR01MB12149.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: BUG: Former primary node might stuck when started as a standby  (Alexander Lakhin <exclusion@gmail.com>)
Responses Re: BUG: Former primary node might stuck when started as a standby
List pgsql-hackers
Dear Alexander,


> FWIW, 004_timeline_switch also failed the past month in the same way [2].

Thanks for the info. So I can provide the patch after the issue for 009_twophase.pl
is fixed. For better understanding we may be able to fork new thread.

> I've just tested 012_subtransactions.pl with the script I proposed at [3]
> and it passed 100 iterations (because it performs $node_primary->stop;
> before $node_standby->promote;, I suppose).

I guess so. cluster::stop does the `pg_ctl stop -m fast` command. In this case
the walsender waits till there are nothing to be sent, see WalSndLoop().
Do let me know if you have observed the similar failure here.

Best regards,
Hayato Kuroda
FUJITSU LIMITED


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Make use of unvolatize() in vac_truncate_clog()
Next
From: Peter Eisentraut
Date:
Subject: Re: Non-text mode for pg_dumpall