Hi @qakapil,

Unfortunately, remote hosts are not supported yet. You could create an instance of PostgresNode and change its host, but it won't do you any good: most of its methods would be useless (e.g. start, stop, get_control_data etc).

How would you solve this problem? Perhaps you could give us an idea.

Hi @funbringer,
Probably we can pass a flag to skip start/stop methods (assuming the DB Cluster on remote host is already up). I will investigate this and let you know.
I have one more question - Is testgres primarily being used to test Postgres extensions ? Does testgres tests more features which installcheck tests (pg_regress) are not testing ?

Thanks,
Kapil.

Is testgres primarily being used to test Postgres extensions ? Does testgres tests more features which installcheck tests (pg_regress) are not testing ?

Currently, yes. For instance, we use it for pg_pathman, pg_shardman, pg_probackup. The main reason is that you can't test streaming replication, sharding, dump/restore etc with linear regression tests.

Now that the questions have been answered, I think we should classify this issue as a feature request.

It should be easy to implement by a library like http://www.paramiko.org/