Re: BUG #6263: \l causes core dump with large database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Robert Messer" <bob(dot)messer(at)l-3com(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6263: \l causes core dump with large database
Date: 2011-10-20 17:35:36
Message-ID: 25402.1319132136@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Robert Messer" <bob(dot)messer(at)l-3com(dot)com> writes:
> postgres=# \l
> *** glibc detected *** /opt/PostgreSQL/9.1/bin/psql.bin: realloc(): invalid
> next size: 0x0000000019510a20 ***

Well, this is interesting, but you're going to need to provide enough
information to let someone else duplicate it. "large database" means
little, and it certainly doesn't explain why you're seeing it when
nobody else has reported any such thing.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2011-10-20 17:50:30 Re: BUG #6263: \l causes core dump with large database
Previous Message Pavel Stehule 2011-10-20 17:33:37 Re: Can't use WITH in a PERFORM query in PL/pgSQL?