Hello,
I changeded shared buffers to 256 MB. But I still receiving the error message.
So I changed to 128 MB, and I received the error again.
I'm using a cursor via ODBC.
Thanks,
Cláudia.
> On Sun, Nov 25, 2007 at 02:53:03AM -0200, claudia.amorim@pcinformatica.com.br
> wrote:
>> I'm having serious problems with PostGreSQL and Windows Server 2003
>> Enterprise Edition. The PostgreSQL Server doesn't start if I set the shared
>> buffers higher than 1GB. All my programs can use only 3 GB of RAM and I have
>> 8GB
>> of RAM.
>> When I monitor the processes I can see that PostGreSQL allocs only 700 MB of
>> memory, and
>> my application 2GB. Total: 3GB.
>
> You do realise that the "shared buffers" only controls the amount of
> memory that is shared. Each backend however can access additional
> memory seperately from all the other processes. So your calculation
> should be 2GB + 700MB *per connection* which can be much higher.
>
>> When I try to execute a query in a table about 4 milion registers, my
>> application crashes with an error message "Out of memory" or
>> "invalid sql statement". But the sql statement is ok - if I execute it
>> in a table with less registers, it works and it is very simple.
>
> My guess is you gave so much memory to shared buffers you did not leave
> enough for normal work. Try reducing your shared buffers to something
> more reasonable, like 256MB or 128MB.
>
> Have a nice day,
> --
> Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
>> Those who make peaceful revolution impossible will make violent revolution
>> inevitable.
>> -- John F Kennedy
>
