| From: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "Ligia María Pimentel C(dot)" <lmpimentel(at)yahoo(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Left join error |
| Date: | 2001-11-06 18:18:13 |
| Message-ID: | web-499892@davinci.ethosmedia.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Ligia,
> Anyhow,... I found that if I write more restrictions on the same
> query, like
> another where, the query responds as I expect. Maybe I was writing
> something
> wrong.
Then it's definitely symptomatic of a memory config problem. I'd say
that when queries get very large, pgsql is trying to use memory that
doesn't exist. Possibilites: you've set shared_buffers or sort_mem much
too high; your machine is chronically low on memory; you have some kind
of kernel config problem; you have a bad RAM card.
Good luck on figuring out which.
-Josh
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh(at)agliodbs(dot)com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gould | 2001-11-06 18:35:06 | Re: copy command with PSQL |
| Previous Message | Jon Obuchowski | 2001-11-06 17:57:06 | trouble using FOR ... IN EXECUTE query LOOPs in PL/pgSQL |