We’ve created System-DSNs (PostgreSQL Unicode) with [Defaults] for both Server.
In MS-ACCESS our biggest Server-Tables (>14.000.000 Rows) can be opened (on both Servers).
But it takes a lot of time and uses a lot of memory - more than 450MBon the client and some GB on the server.
This is for sure MsAcess problem, and not a bug of PostgreSQL.
The indexes are recognized an filtering is fast.
Trying to open more than one “big table” will result in MS-ACCESS “Out of memory”.
Sounds like msAccess fetches all rows and put them into memory which is weird and unwise. Not a bug of PostgreSQL
Sounds like the ODBC driver configuration isn't using UseDeclareFetch=1 and, as such, is defaulting to Postgres' crappy default buffer-all-results-on-the-client-at-once protocol - a problem that would exist in any client software not overriding that behavior.