Remote queries against a Postgres endpoint with timing enabled always says 0 rows returned even when there is data

[MichaelBurgess]

If I execute a query against a remote Postgres endpoint (in this case a Pipes workspace) with .timing on enabled, you always get Rows returned: 0..

I did steampipe login to log in to pipes, then .timing on.

Empty, 0 expected:

> select region from aws_acm_certificate;
+--------+
| region |
+--------+
+--------+

Time: 205ms. Rows returned: 0.

Non-zero, 5 expected:

> select region from aws_s3_bucket limit 5;
+-----------+
| region    |
+-----------+
| us-east-2 |
| us-east-2 |
| us-east-2 |
| us-east-2 |
| us-east-2 |
+-----------+

Time: 186ms. Rows returned: 0.