pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Byron Nikolaidis <byronn@solipsys.com>
To: G. Anthony Reina <reina@nsi.edu>
To: interfaces@postgreSQL.org
Subject: Re: [INTERFACES] psqlODBC/MS Access "Out of memory error (#1)"
Date: Tue, 24 Aug 1999 15:41:50 -0400
Message-ID: <37C2F57E.DE133D21@solipsys.com> (raw)
References: <37C2E032.A6199F3C@nsi.edu>
	<37C2EA1E.D966AC76@solipsys.com>



Byron Nikolaidis wrote:

> "G. Anthony Reina" wrote:
>
> > I just figured out how to get my ODBC connection running between the
> > Postgres 6.5.1 database on my RH Linux 6.0 box and my Windows 95 box. I
> > am using Microsoft Access 97 on the Windows 95 box. I have been able to
> > import some of the smaller tables using "Import from External Data
> > Source" and then specifying the postODBC driver. It seems that some of
> > my larger tables can't be loaded in because of the error:
> >
> > Error while executing the query:
> > Out of memory while reading tuples (#1).
> >
> > The error seems pretty self-explanatory. However, does it mean that I
> > (a) don't have enough system RAM to hold the table, (b) need more hard
> > disk space to hold the file, or (c) none of the above?
> >
>
> Try turning off the declare/fetch driver option.  With this option on, the
> driver is trying to store every single tuple in memory.   With the option
> off, it will only store 100 by default, or the number you enter for the
> cache size.   Since the import is accessing the tuples in a forward-only
> fashion, there is no need to use the declare/fetch.
>
> Byron
>
> ************

Oops, geez, what I meant to say was, turn *ON* the declare/fetch option!!!!
With it *OFF*, the driver is trying to store every single tuple in memory.
With the option *ON", the driver will only store 100 tuples by default, or the
number you enter for the cache size.  Since the import is accessing the tuples
in a forward-only fashion, there is no need for random-access to tuples (so
the declare/fetch *should* be used).

Sorry for any confusion.  I think my mind is still on vacation.

Byron





view thread (3+ messages)

Message-ID: <37C2F57E.DE133D21@solipsys.com>
Permalink:  ../37C2F57E.DE133D21@solipsys.com/
Also on:    postgresql.org/message-id/37C2F57E.DE133D21@solipsys.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: byronn@solipsys.com, reina@nsi.edu, interfaces@postgreSQL.org
  Subject: Re: [INTERFACES] psqlODBC/MS Access "Out of memory error (#1)"
  In-Reply-To: <37C2F57E.DE133D21@solipsys.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox