Re: BUG #5589: psql dies with bad free() in libedit

"Steve Atkins" <steve@blighty.com> writes:
> I have a database that contains two tables (partminer and partminer2), and
> two sequences (partminer2_id_seq and partminer_pk), on a 9.0beta3
> installation built from source with default configure options.
> From psql, entering "\d p<tab>" works as expected. Entering "\d pa<tab>"
> throws an abort from malloc(): "malloc: *** error for object 0x3: pointer
> being freed was not allocated", with the error within libedit.

This sounds a lot like a known bug in Apple's version of libedit:
http://archives.postgresql.org/pgsql-bugs/2010-04/msg00127.php

libedit has proven pretty buggy over the years, and Apple isn't too
speedy to fix it.  The best bet really is to use GNU readline instead.

            regards, tom lane