Re: bogus psql "could not save history file[...]" message in 9.3.6
| От | Alvaro Herrera |
|---|---|
| Тема | Re: bogus psql "could not save history file[...]" message in 9.3.6 |
| Дата | |
| Msg-id | 20150314024619.GJ3291@alvh.no-ip.org обсуждение исходный текст |
| Ответ на | Re: bogus psql "could not save history file[...]" message in 9.3.6 (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: bogus psql "could not save history file[...]" message
in 9.3.6
|
| Список | pgsql-bugs |
Tom Lane wrote:
> Jeff Frost <jeff@pgexperts.com> writes:
> >> On Mar 13, 2015, at 9:56 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> strace'ing psql while it exits might be informative.
>
> > Here you go:
>
> > ...
> > rename("/var/lib/postgresql/.psql_history", "/var/lib/postgresql/.psql_history-") = -1 ENOENT (No such file or
directory)
> > open("/var/lib/postgresql/.psql_history", O_WRONLY|O_CREAT|O_TRUNC, 0600) = 3
> > write(3, "select 1;\n", 10) = 10
> > close(3) = 0
> > unlink("/var/lib/postgresql/.psql_history-") = -1 ENOENT (No such file or directory)
>
> ... WTF? That rename() and that unlink() are certainly not coming from
> Postgres, and I do not see anything like that in the libedit sources
> either. (I'm looking at the libedit-20141030-3.1 version that Fedora
> is currently shipping.) That must be coming from some Ubuntu-specific
> patch?
You can use
apt-get source libedit2
to obtain a copy of the tarball plus all the patches that were applied
to build the package.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-bugs по дате отправления: