This article should help address error messages such as "PSQLException-ERROR: canceling statement due to conflict with recovery" or "FATAL: terminating connection due to conflict with recovery Detail: User query might have needed to see row versions that must be removed. Hint: In a moment you should be able to reconnect to the database and repeat your command. "
This error does not originate in DataVirtuality, rather it has to do with the postgres replication configuration. Usually that means that you are accessing a slave replica which is configured as Hot Standby replica.
In such configuration, the default behavior of Postgres is that any new changes coming from the master server are killing all other queries which use the same data after waiting a very short amount of time, which is 30 seconds per default.
Here are some further infos on the subject:
The way to solve this is for older Potsgres versions is to increase both Postgres parameters discussed here:
A more elegant way to solve this in the newer versions of Postgres is by enabling the parameter hot_standby_feedback, as described here
If none of the above is possible for some reason, for example if the Postgres configuration cannot be changed - in many cases it can be helpful to set retry count on the affected replication job to >1 with delay of several seconds. In this case, the job will retry the operation, and there is a possibilty that on one of the retries no conflict with the master server will occur.