Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XteVc-0001gY-LO for pgsql-general@arkaria.postgresql.org; Wed, 26 Nov 2014 15:28:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XteVc-0003YO-1O for pgsql-general@arkaria.postgresql.org; Wed, 26 Nov 2014 15:28:00 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XteVb-0003YG-09 for pgsql-general@postgresql.org; Wed, 26 Nov 2014 15:27:59 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XteVY-00079q-6q for pgsql-general@postgresql.org; Wed, 26 Nov 2014 15:27:57 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id sAQFRpN2014173; Wed, 26 Nov 2014 10:27:51 -0500 From: Tom Lane To: M Tarkeshwar Rao cc: "pgsql-general@postgresql.org" Subject: Re: issue in postgresql 9.1.3 in using arrow key in Solaris platform In-reply-to: <1C16813DAFF3E44B939586605D40E9F01172038D@ESESSMB107.ericsson.se> References: <1C16813DAFF3E44B939586605D40E9F01172038D@ESESSMB107.ericsson.se> Comments: In-reply-to M Tarkeshwar Rao message dated "Wed, 26 Nov 2014 10:16:57 +0000" Date: Wed, 26 Nov 2014 10:27:51 -0500 Message-ID: <14172.1417015671@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org M Tarkeshwar Rao writes: > We are facing following issue in postgresql 9.1.3 in using arrow key in Solaris platform. > Can you please help us to resolve it or any new release has fix for this or any workaround for this? > issue: psql client generates a core when up arrow is used twice. Almost certainly, this is not psql's fault, but rather a bug in the readline or libedit library it's using for command history. If you're using libedit, I can't say that I'm astonished, as we've seen a depressingly large number of bugs reported in various versions of libedit. In any case, try to get a newer version of that library; or if you've linked psql to libedit, consider rebuilding against libreadline. regards, tom lane PS: this was cross-posted inappropriately. I've trimmed the cc list to just pgsql-general. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general