Re: BUG #5616: psql Doesn't Change Log files on \c - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5616: psql Doesn't Change Log files on \c
Date
Msg-id 7478.1281652393@sss.pgh.pa.us
Whole thread Raw
In response to BUG #5616: psql Doesn't Change Log files on \c  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: BUG #5616: psql Doesn't Change Log files on \c
List pgsql-bugs
"David E. Wheeler" <david@kineticode.com> writes:
> I have this in my .psqlrc:
>     \set HISTFILE ~/.psql_history- :DBNAME
> This is great, except when I change databases in a session:

>     % psql foo
>     foo % \c bar
>     You are now connected to database "bar".
>     SELECT true;

> The last statement will be logged to ~/.psql_history-foo when it should go
> to ~/.psql_history-bar.

I don't think this is a bug.  The history file is read at psql startup
and written out (to the same file name) at exit.  Those operations are
quite expensive, so it would be insane to do them after every backslash
command on the off chance that somebody was expecting to have changed
the effective name of the history file.  (Aside from the cost, this
would greatly increase the race condition hazards from concurrent psql
sessions trying to write the file at the same time.)

            regards, tom lane

pgsql-bugs by date:

Previous
From: "David E. Wheeler"
Date:
Subject: BUG #5616: psql Doesn't Change Log files on \c
Next
From: Fujii Masao
Date:
Subject: Re: Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes