Lou O'Quin wrote:
If this is the case, then I would assume that pgAdmin uses the time sent, the time of first data arrival, and the time of query completion to calculate and display the times on the status line.
We can't know that, because this is hidden in the underlying libpq library.
Is anyone aware of any pgAdmin ideosyncrosy that would explain slow pgAdmin reported execution times when data is transferred over the relatively slow internet?
On slow machines, the update of the status line may take considerable time (100 per second), this will be addressed in V1.4. But this has nothing to do with slow lines.
Regards, Andreas
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
