Re: BUG #5899: Memory corruption when running psql - Mailing list pgsql-bugs

From Robert Haas
Subject Re: BUG #5899: Memory corruption when running psql
Date
Msg-id AANLkTi=ftRhyZ3fH4YooFhT56JwEBjD4rGXUHqEp4v+2@mail.gmail.com
Whole thread Raw
In response to Re: BUG #5899: Memory corruption when running psql  (Ross Barrett <ross_barrett@rapid7.com>)
Responses Re: BUG #5899: Memory corruption when running psql  (SandraA <ArnoldS@osti.gov>)
List pgsql-bugs
On Thu, Mar 3, 2011 at 11:14 AM, Ross Barrett <ross_barrett@rapid7.com> wro=
te:
> I determined that this issue was caused by something (a large error messa=
ge
> relating to failed delete caused by an integrity issue) which I erroneous=
ly
> pasted into the psql terminal. =A0I 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.  :-(

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

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: BUG #5863: help message report 5433 as default port
Next
From: Robert Haas
Date:
Subject: Re: Corrupted index on 9.0.3 streaming hot standby