BUG #7803: Replication Problem(no master is there)

The following bug has been logged on the website:

Bug reference:      7803
Logged by:          Tomonari Katsumata
Email address:      katsumata.tomonari@po.ntts.co.jp
PostgreSQL version: 9.2.2
Operating system:   RHEL 5.3 x86_64
Description:        =


hi, I'm playing with Synchronous Replication on PostgreSQL 9.2.2.
And I saw a strange behavior.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
[issues]
two standbys are connected on each other, but
no master is there.


[reproduce]
1. create a master on port 22922

--- postgresql.conf ---
wal_level =3D hot_standby
archive_mode =3D on
archive_command =3D 'cp %p ${PGARC}/%f'
max_wal_senders =3D 3
listen_addresses =3D '*'
hot_standby =3D on
------------------------

2. start the master

mst$ pg_ctl start

3. create a standby(taking a base backup from master)

pg_basebackup -p 22922 -D ${PGDATA}

-- recovery.conf --
restore_command =3D 'cp ${PGARC}/%f %p'
standby_mode =3D on
primary_conninfo =3D 'port=3D22922 application_name=3Dsby'
recovery_target_timeline =3D 'newest'
-------------------

4. stop the master

mst$ pg_ctl stop

5. make recovery.conf for the master

-- recovery.conf --
restore_command =3D 'cp ${PGARC}/%f %p'
standby_mode =3D on
primary_conninfo =3D 'port=3D23922 application_name=3Dsby'
recovery_target_timeline =3D 'newest'
-------------------

6. start the master as standby

mst$ pg_ctl start

7. start the standby as standby on port 23922

sby$ pg_ctl start
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

I did not see the situation like above on PostgreSQL 9.1.7.

Is this intended change?


regards,
-----------------
NTT Software Corporation
 Tomonari Katsumata