BUG #6571: Postgres Kills 'Select 1' query randomly on hot standby databases

The following bug has been logged on the website:

Bug reference: 6571
Logged by: Alex Matzinger
Email address: amatzinger(at)experts-exchange(dot)com
PostgreSQL version: 9.1.2
Operating system: Freebsd 7.4
Description:

On a hot standby database, while the primary is being updated, Postgres will
randomly kill a process which is performing a "Select 1" command.

The error is this:
2012-04-02 13:36:13.269
PDT,"smxuser","smxprd1",39523,"127.0.0.1:57893",4f79ffad.9a63,1,"",2012-04-02
12:36:13 PDT,3/32,0,FATAL,40001,"terminating connection due to conflict with
recovery","User query might have needed to see row versions that must be
removed.","In a moment you should be able to reconnect to the database and
repeat your command.",,,,,,,""

We have 5 hot standby's set up, which all preform this SELECT 1, and
postgres kills them across all standby's.

There should never be a situation that SELECT 1 is in conflict with data, as
it it never using any table in the database.

We will be updating to 9.1.3 very soon, but i have not seen any
documentation that this issue is corrected, or even known.