Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id BEBD0B5DBD5 for ; Sat, 28 May 2011 05:33:01 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 48372-04 for ; Sat, 28 May 2011 08:32:54 +0000 (UTC) X-Greylist: delayed 01:55:35.506189 by SQLgrey-1.7.6 Received: from dime159.dizinc.com (dime159.dizinc.com [66.7.216.77]) by mail.postgresql.org (Postfix) with ESMTP id 5EA70B5DBD1 for ; Sat, 28 May 2011 05:32:54 -0300 (ADT) Received: from [200.32.232.149] (port=55976 helo=mark-laptop.turnkey.local) by dime159.dizinc.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1QQD98-0002BN-7a for pgsql-admin@postgresql.org; Sat, 28 May 2011 02:37:14 -0400 Message-ID: <4DE09814.6030209@turnkey.bz> Date: Sat, 28 May 2011 00:37:08 -0600 From: "M. D." User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110414 SUSE/3.1.10 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: library problem with psql Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - dime159.dizinc.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - turnkey.bz X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201105/173 X-Sequence-Number: 37610 Hi, I just did an upgrade on a server from 8.4.4 to 9.0.4. I used EnterpiseDB's binary packages. Everything seems to be running good, but when I run psql, any command will give me a memory dump exactly like in this post: http://forums.enterprisedb.com/posts/list/2604.page#9753 Should I revert to using the old database, or is this problem just a psql problem? I can live without psql for a few days till I find a solution. Just tested pg_dump and it works fine. Mark