From: | "Pavlo Golub" <pavlo(dot)golub(at)cybertec(dot)at> |
---|---|
To: | "Stefan Wolf" <sw(at)zpmt(dot)de>, pgsql-interfaces(at)lists(dot)postgresql(dot)org |
Subject: | Re: MS-ACCESS 2010, ODBC 12.01, Out of Memory |
Date: | 2020-03-02 14:43:32 |
Message-ID: | em17d87dc7-445c-42bf-b1d9-e57745f8f3f5@pg-desktop |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
------ Original Message ------
From: "Stefan Wolf" <sw(at)zpmt(dot)de>
To: pgsql-interfaces(at)lists(dot)postgresql(dot)org
Sent: 2020-03-02 15:41:05
Subject: MS-ACCESS 2010, ODBC 12.01, Out of Memory
>Win10-Client: MS-ACCESS 2010 (32-Bit), ODBC-Driver: 12.01
>
>Linux-Server (1): PostgreSQL 12.2
>
>Linux-Server (2): PostgreSQL 9.6
>
>
>
>
>
>We are currently migrating from PG 9.6. to 12.x.
>
>
>
>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
>
>
>
>
>Best regards
>
>-Stefan Wolf-
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jonah H. Harris | 2020-03-02 15:23:19 | Re: MS-ACCESS 2010, ODBC 12.01, Out of Memory |
Previous Message | Stefan Wolf | 2020-03-02 14:41:05 | MS-ACCESS 2010, ODBC 12.01, Out of Memory |