| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: bogus psql "could not save history file[...]" message in 9.3.6 |
| Date: | 2015-03-14 01:56:42 |
| Message-ID: | 31313.1426298202@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
>> \q # 'could not save history to file "/var/lib/postgresql/.psql_history":
> No such file or directory' !!!
BTW, I poked around in the libedit sources and noted that it will call
wctomb() during write_history(), assuming it's configured to support wide
characters. Working hypothesis is that wctomb() is trying to read some
locale configuration file and not finding it, which it's probably okay
with, but our is-errno-set check is unhappy later. This behavior might
well vary depending on what locale environment you have set.
strace'ing psql while it exits might be informative.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Frost | 2015-03-14 02:02:17 | Re: bogus psql "could not save history file[...]" message in 9.3.6 |
| Previous Message | David G. Johnston | 2015-03-14 01:55:18 | Re: bogus psql "could not save history file[...]" message in 9.3.6 |