Re: Invalid memory alloc request size - Mailing list pgsql-performance

From Samuel Gendler
Subject Re: Invalid memory alloc request size
Date
Msg-id CAEV0TzADwABjM4GR6LdCdr_CD+-jJ3g9AsGDtdGBTYJ65hwvpw@mail.gmail.com
Whole thread Raw
In response to Invalid memory alloc request size  (Mahavir Trivedi <mahavir.trivedi@gmail.com>)
List pgsql-performance
This was answered on the list last time you asked it. You are exceeding a maximum buffer size. There was an implication that it was related to converting a string from one encoding to another that could maybe be alleviated by using the same encoding in both client and server, but a more reliable solution is probably breaking your sql file into smaller pieces (or, perhaps even better would be bulk-loading the data via COPY, assuming that isn't subject to the same buffer size limitation ). I suppose you could investigate recompiling postgresql with a larger buffer, though that is likely to have side effects that i certainly can't predict.



On Wed, Oct 31, 2012 at 3:24 AM, Mahavir Trivedi <mahavir.trivedi@gmail.com> wrote:
dear friends

i have - sql file of size more than 1 gb 
when i execute it  then after some time "Invalid memory alloc request size 100234023 byte"   occcured
what ' s problem that i don't know ?



with thanks
mahavir

pgsql-performance by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Invalid memory alloc request size
Next
From: Vincenzo Melandri
Date:
Subject: Seq scan on big table, episode 2