Re: [GENERAL] Out of memory with ODBC

2007-10-22 Thread Richard Huxton
Relyea, Mike wrote: After setting log_statement = 'all', I ran my query using pgAdmin, and then ran the query using Access. I now had all of the commands sent to the DB by each application. Remember, *something* in the sequence of commands that get executed from Access must be different than

Re: [GENERAL] Out of memory with ODBC

2007-10-19 Thread Relyea, Mike
> From: Richard Huxton [mailto:[EMAIL PROTECTED] > Relyea, Mike wrote: > > This seems to be a problem with the ODBC driver? How can I narrow > > that down further? > > Well, first make 100% certain the query being executed is the > one you see being sent from Access. I did by setting log_stat

Re: [GENERAL] Out of memory with ODBC

2007-10-12 Thread Relyea, Mike
> From: Richard Huxton [mailto:[EMAIL PROTECTED] > Relyea, Mike wrote: > > This seems to be a problem with the ODBC driver? How can I narrow > > that down further? > > Well, first make 100% certain the query being executed is the > one you see being sent from Access. > > If so, the next obvio

Re: [GENERAL] Out of memory with ODBC

2007-10-12 Thread Richard Huxton
Relyea, Mike wrote: From: Richard Huxton [mailto:[EMAIL PROTECTED] Do you see a backend process growing to 2GB+ before failure? I'm running PG 8.2.4 on WinXP. I used the task manager (as a quick and dirty utility) to watch the memory usage of the backend and it seemed to peak around 1.2GB.

Re: [GENERAL] Out of memory with ODBC

2007-10-12 Thread Relyea, Mike
> From: Richard Huxton [mailto:[EMAIL PROTECTED] > > MessageContext: 1946198040 total in 258 blocks; 26624 free (43 > > chunks); > > 1946171416 used > > Well, I don't have to be a developer to know that if there's > a memory problem it's that big number starting 1946... that's > the problem. I

Re: [GENERAL] Out of memory with ODBC

2007-10-12 Thread Richard Huxton
Tom Lane wrote: Richard Huxton <[EMAIL PROTECTED]> writes: Hmm - I can't think how that could reach 1.9GB in size, especially since it has to be something different between a "raw" connection and how ODBC is doing things. Try turning on log_statement to see what's really being executed. I see

Re: [GENERAL] Out of memory with ODBC

2007-10-12 Thread Tom Lane
Richard Huxton <[EMAIL PROTECTED]> writes: > Hmm - I can't think how that could reach 1.9GB in size, especially since > it has to be something different between a "raw" connection and how ODBC > is doing things. Try turning on log_statement to see what's really being executed. I seem to recall r

Re: [GENERAL] Out of memory with ODBC

2007-10-12 Thread Richard Huxton
Relyea, Mike wrote: From: Richard Huxton [mailto:[EMAIL PROTECTED] Relyea, Mike wrote: If I execute this query in PGAdmin III it runs without any errors and returns no records. Hmm. So what's different about the queries? Nothing. The SQL is identical. I copied out of the log file and pas

Re: [GENERAL] Out of memory with ODBC

2007-10-12 Thread Relyea, Mike
> From: Richard Huxton [mailto:[EMAIL PROTECTED] > > Relyea, Mike wrote: >> If I execute this query in PGAdmin III it runs without any errors and returns no records. > > Hmm. So what's different about the queries? > Nothing. The SQL is identical. I copied out of the log file and pasted into

Re: [GENERAL] Out of memory with ODBC

2007-10-12 Thread Richard Huxton
Relyea, Mike wrote: I tried posting this to the OBC list but didn't get any responses, so I'm trying my luck here. I'm receiving an out of memory error when trying to execute a long, complex query involving many temp tables. I'm using psqlODBC ver 8.02.0500 and PG 8.2.4 on WinXP. I'm trying