Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA27196 for ; Fri, 26 Nov 1999 11:20:59 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id LAA15893; Fri, 26 Nov 1999 11:20:24 -0500 (EST) To: "Emils Klotins" cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] Backend dies (6.5.3-1) on SELECT from 6 row table In-reply-to: Your message of Fri, 26 Nov 1999 14:35:56 EET <12273905952244@bkc.lv> Date: Fri, 26 Nov 1999 11:20:24 -0500 Message-ID: <15891.943633224@sss.pgh.pa.us> From: Tom Lane "Emils Klotins" writes: > When I try to "SELECT * FROM most of the tables (except for > ones which have 2 or less rows) , the backend dies: > If i try to select specific field (address_id or lastname, > firstname from the same table - it works). That's really odd. I doubt you have a memory problem; corrupted data or maybe an outright bug of some kind seem more likely. What error message, if any, shows up in the postmaster log file? Also, the crashed backend presumably leaves a core file in the database directory. Do you know how to use gdb to get a backtrace showing what the backend was doing? Briefly it's gdb path/to/postgres path/to/core bt quit regards, tom lane