Re: BUG #5899: Memory corruption when running psql

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Ross Barrett <ross_barrett(at)rapid7(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5899: Memory corruption when running psql
Date: 2011-03-03 17:06:07
Message-ID: AANLkTi=ftRhyZ3fH4YooFhT56JwEBjD4rGXUHqEp4v+2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Mar 3, 2011 at 11:14 AM, Ross Barrett <ross_barrett(at)rapid7(dot)com> wrote:
> I determined that this issue was caused by something (a large error message
> relating to failed delete caused by an integrity issue) which I erroneously
> pasted into the psql terminal.  I was able to get around the problem by
> deleting my .pg_history file.
>
> Perhaps it is more accurate that this is a problem with termcap?

More likely libedit, which FWICT seems to be riddled with bugs. :-(

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2011-03-03 17:09:26 Re: Corrupted index on 9.0.3 streaming hot standby
Previous Message Robert Haas 2011-03-03 17:05:05 Re: BUG #5863: help message report 5433 as default port