Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28]) by postgresql.org (8.11.3/8.11.1) with SMTP id f4IClXA36914 for ; Fri, 18 May 2001 08:47:33 -0400 (EDT) (envelope-from pgsql-sql-owner@postgresql.org) Received: from news.tht.net (news.hub.org [216.126.91.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4GMvMA51201 for ; Wed, 16 May 2001 18:57:22 -0400 (EDT) (envelope-from news@news.tht.net) Received: (from news@localhost) by news.tht.net (8.11.1/8.11.1) id f4GMVWu83763 for pgsql-sql@postgresql.org; Wed, 16 May 2001 18:31:32 -0400 (EDT) (envelope-from news) From: "Ligia Pimentel" X-Newsgroups: comp.databases.postgresql.sql Subject: Re: fatal ERROR running simple join query... Date: Wed, 16 May 2001 16:29:57 -0500 Organization: . Lines: 62 Message-ID: <9duv41$2hpg$1@news.tht.net> References: <989853716.3afff814ad799@bugs.unl.edu.ar> Reply-To: "Ligia Pimentel" X-Complaints-To: scrappy@hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 To: pgsql-sql@postgresql.org X-Archive-Number: 200105/194 X-Sequence-Number: 3011 It didn't work. I checked the tables (both) and found nothing wrong. Finally I received an e-mail from Tom Lane suggesting that I upgraded to Postgres 7.1, wich I did. After the upgrade, everything worked just fine. Thank you. Ligia "Martín Marqués" wrote in message news:989853716.3afff814ad799@bugs.unl.edu.ar... > Quoting Ligia Pimentel : > > > > > I have a problem with postgres, I'm running a query that joins two tables, > > one with 129000+ records, and the other with 1172 records, it's a very > > simple join. But postgres can't handle it!!! (Both tables have an index on > > the field "cuentacb"). > > > > I get the following error after 3 minutes... > > > > migracion=# select * from cuentasequivalentes, equiv11mayo m > > migracion-# where cuentasequivalentes.cuentacb = m.cuentacb > > migracion-# and cuentasequivalentes.cuentabr <> m.cuentabr; > > FATAL 1: Memory exhausted in AllocSetAlloc() > > pqReadData() -- backend closed the channel unexpectedly. > > This probably means the backend terminated abnormally > > before or while processing the request. > > The connection to the server was lost. Attempting reset: Succeeded. > > First you should run VACUUM analyze on that database, or at least on those 2 > tables. Check with EXPLAIN to see how much better the queries get after the > analyze. > > > What can I do? I'm guessing that I could change a configuration parameter > > or > > something like that, but I don't know. > > There are so many parameters to change, that I have to tell you to go and see > the "PostgreSQL 7.1 Administrator's Guide". > > Saludos... :-) > > -- > El mejor sistema operativo es aquel que te da de comer. > Cuida tu dieta. > ----------------------------------------------------------------- > Martin Marques | mmarques@unl.edu.ar > Programador, Administrador | Centro de Telematica > Universidad Nacional > del Litoral > ----------------------------------------------------------------- > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html