PostGIS topology functions are different to pgRouting's network topology. pgRouting's topology is very simple and it allows for example intersecting linestrings, which would cause an error with PostGIS topology vaalidation. In fact pgRouting only needs valid source and target ID's to describe the network.

That said, a typical problem might be disconnected linestrings, but pgr_createtopology has a "snapping tolerance" parameter, that treats two lines as connected automatically, if their start and/or end points are very close. http://docs.pgrouting.org/latest/en/pgr_createTopology.html#pgr-create-topology

And there are a few other "Topology Functions", that may be helpful to identify errors, see: http://docs.pgrouting.org/latest/en/topology-functions.html#topology-functions

These functions do not fix problems automatically, but you eventually can use their results to do so.

PostGIS topology functions are different to pgRouting's network topology. pgRouting's topology is very simple and it allows for example intersecting linestrings, which would cause an error with PostGIS topology validation. In fact pgRouting only needs valid source and target ID's to describe the network.

That said, a typical problem might be disconnected linestrings, but pgr_createtopology has a "snapping tolerance" parameter, that treats two lines as connected automatically, if their start and/or end points are very close. http://docs.pgrouting.org/latest/en/pgr_createTopology.html#pgr-create-topology

And there are a few other "Topology Functions", that may be helpful to identify errors, see: http://docs.pgrouting.org/latest/en/topology-functions.html#topology-functions

These functions do not fix problems automatically, but you eventually can use their results to do so.