Re: BUG #12300: ~/.psql_history nonexistent warning on first run

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dzmitry Lazerka <dlazerka(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #12300: ~/.psql_history nonexistent warning on first run
Date: 2014-12-22 02:00:41
Message-ID: 21618.1419213641@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Dzmitry Lazerka <dlazerka(at)gmail(dot)com> writes:
> I have `history` available, but nor `readline`, nor `libedit` available as
> commands in my bash.

That's not particularly relevant, because what we're talking about here is
libraries not shell commands.

Applying ldd to the psql executable might yield something informative.
On my machine for instance I get

...
libreadline.so.6 => /lib64/libreadline.so.6 (0x0000003ad8e00000)
...

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message dhalperi 2014-12-22 20:04:03 BUG #12319: NPE in JDBC driver when using PgCopyOutputStream
Previous Message Dzmitry Lazerka 2014-12-22 01:52:16 Re: BUG #12300: ~/.psql_history nonexistent warning on first run