The topic for this message would be better suited for the
pgsql-general or pgsql-admin mailing lists since the problem you've
described doesn't relate to the ODBC driver.
If you re-post your email to those mailing lists you will not doubt
get more feed back.
On Mon, Nov 16, 2009 at 8:26 AM, Maria Cianci <Maria(dot)Cianci(at)cae(dot)com> wrote:
> I am running on a Windows XP machine, 4GB of RAM and over 26GB of free
> hard-disk an application that all it does is insert records into the
> Postgres 8.3 database. When the database is approx 17GB Postgres issues the
> “Not enough storage is available to complete this operation” and refuses to
> insert records. I normally shut down and restart the application and data
> collection continues normally until it reaches the 26GB and issues the same
> error: “Not enough storage is available to complete this operation.” I’m
> very puzzled to say the least. The Postgres configuration is attached. For
> some reason Postgres would no load if shared_buffers > 900MB.
> I should say that my Windows is running with the /3GB flag.
> Thanks in advance for any help you can offer.
Richard Broersma Jr.
Visit the Los Angeles PostgreSQL Users Group (LAPUG)
In response to
pgsql-odbc by date
|Next:||From: Hiroshi Inoue||Date: 2009-11-17 16:16:54|
|Subject: Re: Undesired decimal truncation with psqlodbc version 08.04.0100|
|Previous:||From: Maria Cianci||Date: 2009-11-16 16:26:10|
|Subject: Postgres issues "Not enough storage is available to complete this operation" exception|