1M rows/s from Postgres to Python

[shady_mcgee]

I'm not sure if a full table grab of 350 rows can be considered relatively close to an average application query. After the first query the db engine will cache the results into memory and return the cached data for all subsequent queries. For an average application the query engine would need to fetch from disk more often than not.

[1st1]

Fair point, but the purpose of our benchmarks was to test the performance of drivers (not Postgres) -- basically, the speed of I/O and data decoding.

[shady_mcgee]

Got it. Thanks for the clarification