BUG #5052: lost history

Started by Marek Wójtowiczover 16 years ago4 messagesbugs
Jump to latest
#1Marek Wójtowicz
wumarex@agh.edu.pl

The following bug has been logged online:

Bug reference: 5052
Logged by:
Email address: wumarex@agh.edu.pl
PostgreSQL version: 8.4.1
Operating system: Linux
Description: lost history
Details:

When I will start simultaneously more than time psql program, it after the
outing is staying history of only this session which we left recently.

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Marek Wójtowicz (#1)
Re: BUG #5052: lost history

"" <wumarex@agh.edu.pl> writes:

When I will start simultaneously more than time psql program, it after the
outing is staying history of only this session which we left recently.

Yeah, that's libreadline's fault :-(. You should complain to the
readline authors.

regards, tom lane

#3Marek Wójtowicz
wumarex@agh.edu.pl
In reply to: Tom Lane (#2)
Re: BUG #5052: lost history

Dnia niedziela, 13 września 2009, napisano:

"" <wumarex@agh.edu.pl> writes:

When I will start simultaneously more than time psql program, it after
the outing is staying history of only this session which we left
recently.

Yeah, that's libreadline's fault :-(. You should complain to the
readline authors.

bash using same version libreadline and dont't have this problem :-)

--

Marek Wójtowicz <wumarex@agh.edu.pl>
http://galaxy.uci.agh.edu.pl/~wumarex/

#4Tom Lane
tgl@sss.pgh.pa.us
In reply to: Marek Wójtowicz (#3)
Re: BUG #5052: lost history

Marek =?iso-8859-2?q?W=F3jtowicz?= <wumarex@agh.edu.pl> writes:

Yeah, that's libreadline's fault :-(. You should complain to the
readline authors.

bash using same version libreadline and dont't have this problem :-)

[ pokes around... ] Hmm, it looks like bash is using append_history()
which has been added to readline since the 4.x days. (It's there in
5.2; can't find any info about when it went in.) Probably would be
worth adding a configure test so we can use this ...

regards, tom lane