Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fA6IIFm83799 for ; Tue, 6 Nov 2001 13:18:16 -0500 (EST) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.7) with HTTP id 499892; Tue, 06 Nov 2001 10:18:13 -0800 From: "Josh Berkus" Subject: Re: Left join error To: "Ligia =?ISO-8859-1?Q?Mar=EDa?= Pimentel C." Cc: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.7 Date: Tue, 06 Nov 2001 10:18:13 -0800 Message-ID: In-Reply-To: <002101c166e4$1a175d40$0d11c89b@bancoreformador.com> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200111/71 X-Sequence-Number: 5455 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@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco