Re: [PERFORM] Problems with PostGreSQL and Windows 2003

2007-11-26 Thread Heikki Linnakangas
There is no mention of Out of Memory in that piece of log. [EMAIL PROTECTED] wrote: Hi, I'm using a cursor. Here is the a piece of log file (psqlodbc): [0.000]conn=02DE3A70, PGAPI_DriverConnect( in)='DSN=BI;UID=biuser;PWD=x;', fDriverCompletion=0 [0.000]DSN info: DSN='BI',server='loca

Re: [PERFORM] Problems with PostGreSQL and Windows 2003

2007-11-25 Thread claudia . amorim
Hi, I'm using a cursor. Here is the a piece of log file (psqlodbc): [0.000]conn=02DE3A70, PGAPI_DriverConnect( in)='DSN=BI;UID=biuser;PWD=x;', fDriverCompletion=0 [0.000]DSN info: DSN='BI',server='localhost',port='5432',dbase='BI',user='biuser',passwd='x' [0.000] onlyread='0

Re: [PERFORM] Problems with PostGreSQL and Windows 2003

2007-11-25 Thread Scott Marlowe
Are you then trying to process the whole data set at once? I'm pretty certain the issue is your app, not pgsql, running out of memory. ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

Re: [PERFORM] Problems with PostGreSQL and Windows 2003

2007-11-25 Thread claudia . amorim
I'm already using a cursor via ODBC. > On Nov 24, 2007 10:57 PM, <[EMAIL PROTECTED]> wrote: >> Hello, >> >>I forgot to say that I changed work_mem to 16 MB but I didn't have >> sucess. >> I received the same >> error message. > > The error message you're getting is from your client bec

Re: [PERFORM] Problems with PostGreSQL and Windows 2003

2007-11-24 Thread Scott Marlowe
On Nov 24, 2007 10:57 PM, <[EMAIL PROTECTED]> wrote: > Hello, > >I forgot to say that I changed work_mem to 16 MB but I didn't have > sucess. > I received the same > error message. The error message you're getting is from your client because it's getting too big of a result set back at onc

Re: [PERFORM] Problems with PostGreSQL and Windows 2003

2007-11-24 Thread claudia . amorim
Hello, I forgot to say that I changed work_mem to 16 MB but I didn't have sucess. I received the same error message. Thanks, Cláudia Amorim. > Hi, > > When I set shared buffers higher than 1GB, PostGreSQL doens't start. > > When my application crashes I receive a message "Out of memory"

Re: [PERFORM] Problems with PostGreSQL and Windows 2003

2007-11-24 Thread claudia . amorim
Hi, When I set shared buffers higher than 1GB, PostGreSQL doens't start. When my application crashes I receive a 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. When I monitor the pr

Re: [PERFORM] Problems with PostGreSQL and Windows 2003

2007-11-24 Thread Heikki Linnakangas
[EMAIL PROTECTED] wrote: I'm having serious peformance problems with PostGreSQL and Windows Server 2003 Enterprise Edition. The PostgreSQL Server don't starts if I set the shared buffers high than 1GB. All my programs can use only 3 GB of RAM and I have 8GB of RAM. When I try to execute a query i

[PERFORM] Problems with PostGreSQL and Windows 2003

2007-11-23 Thread claudia . amorim
Hello, I'm having serious peformance problems with PostGreSQL and Windows Server 2003 Enterprise Edition. The PostgreSQL Server don't starts if I set the shared buffers high than 1GB. All my programs can use only 3 GB of RAM and I have 8GB of RAM. When I try to execute a query in a table about 4