Postgres Pro
Downloads
Home   >   mailing lists

Re: MS-ACCESS 2010, ODBC 12.01, Out of Memory - Mailing list pgsql-interfaces

From Pavlo Golub
Subject Re: MS-ACCESS 2010, ODBC 12.01, Out of Memory
Date
Msg-id em17d87dc7-445c-42bf-b1d9-e57745f8f3f5@pg-desktop
Whole thread Raw
In response to MS-ACCESS 2010, ODBC 12.01, Out of Memory  ("Stefan Wolf" <sw@zpmt.de>)
Responses Re: MS-ACCESS 2010, ODBC 12.01, Out of Memory  ("Jonah H. Harris" <jonah.harris@gmail.com>)
List pgsql-interfaces
Tree view

------ Original Message ------
From: "Stefan Wolf" <sw@zpmt.de>
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.

 

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-

 

pgsql-interfaces by date:

Previous
From: "Stefan Wolf"
Date:
Subject: MS-ACCESS 2010, ODBC 12.01, Out of Memory
Next
From: "Jonah H. Harris"
Date:
Subject: Re: MS-ACCESS 2010, ODBC 12.01, Out of Memory