public inbox for [email protected]help / color / mirror / Atom feed
MS-ACCESS 2010, ODBC 12.01, Out of Memory 3+ messages / 3 participants [nested] [flat]
* MS-ACCESS 2010, ODBC 12.01, Out of Memory @ 2020-03-02 14:41 Stefan Wolf <[email protected]> 2020-03-02 14:43 ` Re: MS-ACCESS 2010, ODBC 12.01, Out of Memory Pavlo Golub <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Stefan Wolf @ 2020-03-02 14:41 UTC (permalink / raw) To: [email protected] 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 450MB on the client and some GB on the server. The indexes are recognized an filtering is fast. Trying to open more than one "big table" will result in MS-ACCESS "Out of memory". Best regards -Stefan Wolf- ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: MS-ACCESS 2010, ODBC 12.01, Out of Memory 2020-03-02 14:41 MS-ACCESS 2010, ODBC 12.01, Out of Memory Stefan Wolf <[email protected]> @ 2020-03-02 14:43 ` Pavlo Golub <[email protected]> 2020-03-02 15:23 ` Re: MS-ACCESS 2010, ODBC 12.01, Out of Memory Jonah H. Harris <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Pavlo Golub @ 2020-03-02 14:43 UTC (permalink / raw) To: Stefan Wolf <[email protected]>; [email protected] ------ Original Message ------ From: "Stefan Wolf" <[email protected]> To: [email protected] 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- > > > ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: MS-ACCESS 2010, ODBC 12.01, Out of Memory 2020-03-02 14:41 MS-ACCESS 2010, ODBC 12.01, Out of Memory Stefan Wolf <[email protected]> 2020-03-02 14:43 ` Re: MS-ACCESS 2010, ODBC 12.01, Out of Memory Pavlo Golub <[email protected]> @ 2020-03-02 15:23 ` Jonah H. Harris <[email protected]> 0 siblings, 0 replies; 3+ messages in thread From: Jonah H. Harris @ 2020-03-02 15:23 UTC (permalink / raw) To: Pavlo Golub <[email protected]>; +Cc: Stefan Wolf <[email protected]>; [email protected] On Mon, Mar 2, 2020 at 9:43 AM Pavlo Golub <[email protected]> wrote: > > ------ Original Message ------ > From: "Stefan Wolf" <[email protected]> > To: [email protected] > 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 450MB on > the client and some GB on the server. > > > This is for sure MsAcess problem, and not a bug of PostgreSQL. > Is it? > > 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. -- Jonah H. Harris ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2020-03-02 15:23 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2020-03-02 14:41 MS-ACCESS 2010, ODBC 12.01, Out of Memory Stefan Wolf <[email protected]> 2020-03-02 14:43 ` Pavlo Golub <[email protected]> 2020-03-02 15:23 ` Jonah H. Harris <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox