A method, implemented at least in part by a database system node comprising a processing unit and memory (2320, 2325, 2340), the database system node being one of a plurality of database system nodes and being in communication with at least a portion of the plurality of database system nodes and with a database client (110, 1004, 1104, 1204, 1304, 1404, 1504, 1604), at least one of the plurality of database system nodes being a source node (120, 210, 302, 704, 804, 904, 1008, 1120, 1208, 1308, 1408, 1508, 1608) and at least one of the plurality of database system nodes being a replica node (130, 220, 230, 304, 306, 708, 808, 908, 1012, 1124, 1128, 1212, 1216, 1312, 1316, 1412, 1416, 1512, 1516, 1612, 1616), the method comprising: determining that an availability status of the replica node (130, 220, 230, 304, 306, 708, 808, 908, 1012, 1124, 1128, 1212, 1216, 1312, 1316, 1412, 1416, 1512, 1516, 1612, 1616) has changed; receiving a prepared statement (1028, 1108) from the database client (110, 1004, 1104, 1204, 1304, 1404, 1504, 1604), the prepared statement (1028, 1108) specifying one or more nodes useable to execute the prepared statement (1028, 1108); updating the prepared statement (1028, 1108), the updating comprising adding a node to the one or more nodes in the prepared statement (1028, 1108), or removing at least one of the one or more nodes in the prepared statement (1028, 1108), depending on the type of availability status change of the replica node (130, 220, 230, 304, 306, 708, 808, 908, 1012, 1124, 1128, 1212, 1216, 1312, 1316, 1412, 1416, 1512, 1516, 1612, 1616); and sending the updated prepared statement (1028, 1108) to the database client (110, 1004, 1104, 1204, 1304, 1404, 1504, 1604); characterized in that the method further comprises: in response to determining that the availability status of the replica node (130, 220, 230, 304, 306, 708, 808, 908, 1012, 1124, 1128, 1212, 1216, 1312, 1316, 1412, 1416, 1512, 1516, 1612, 1616) has changed, incrementing an identifier (1040, 1132) maintained by the database system node; comparing the incremented identifier (1040, 1132) with a version timestamp associated with the prepared statement (1028, 1108); and determining that the version timestamp identifier is associated with an earlier state of the database system (100, 1000) than a state of the database system (100, 1000) associated with the incremented identifier (1040, 1132); wherein the updating is carried out in response to determining that the version timestamp identifier is associated with an earlier state of the database system (100, 1000). determining that an availability status of the replica node (130, 220, 230, 304, 306, 708, 808, 908, 1012, 1124, 1128, 1212, 1216, 1312, 1316, 1412, 1416, 1512, 1516, 1612, 1616) has changed; receiving a prepared statement (1028, 1108) from the database client (110, 1004, 1104, 1204, 1304, 1404, 1504, 1604), the prepared statement (1028, 1108) specifying one or more nodes useable to execute the prepared statement (1028, 1108); updating the prepared statement (1028, 1108), the updating comprising adding a node to the one or more nodes in the prepared statement (1028, 1108), or removing at least one of the one or more nodes in the prepared statement (1028, 1108), depending on the type of availability status change of the replica node (130, 220, 230, 304, 306, 708, 808, 908, 1012, 1124, 1128, 1212, 1216, 1312, 1316, 1412, 1416, 1512, 1516, 1612, 1616); and sending the updated prepared statement (1028, 1108) to the database client (110, 1004, 1104, 1204, 1304, 1404, 1504, 1604); characterized in that the method further comprises: in response to determining that the availability status of the replica node (130, 220, 230, 304, 306, 708, 808, 908, 1012, 1124, 1128, 1212, 1216, 1312, 1316, 1412, 1416, 1512, 1516, 1612, 1616) has changed, incrementing an identifier (1040, 1132) maintained by the database system node; comparing the incremented identifier (1040, 1132) with a version timestamp associated with the prepared statement (1028, 1108); and determining that the version timestamp identifier is associated with an earlier state of the database system (100, 1000) than a state of the database system (100, 1000) associated with the incremented identifier (1040, 1132); wherein the updating is carried out in response to determining that the version timestamp identifier is associated with an earlier state of the database system (100, 1000). in response to determining that the availability status of the replica node (130, 220, 230, 304, 306, 708, 808, 908, 1012, 1124, 1128, 1212, 1216, 1312, 1316, 1412, 1416, 1512, 1516, 1612, 1616) has changed, incrementing an identifier (1040, 1132) maintained by the database system node; comparing the incremented identifier (1040, 1132) with a version timestamp associated with the prepared statement (1028, 1108); and determining that the version timestamp identifier is associated with an earlier state of the database system (100, 1000) than a state of the database system (100, 1000) associated with the incremented identifier (1040, 1132); wherein the updating is carried out in response to determining that the version timestamp identifier is associated with an earlier state of the database system (100, 1000).