Re: psql 'none' as a HISTFILE special case - Mailing list pgsql-patches

From Martin Atukunda
Subject Re: psql 'none' as a HISTFILE special case
Date
Msg-id ce92d7150608250803x7861d577ob50a40ff5625ab46@mail.gmail.com
Whole thread Raw
In response to Re: psql 'none' as a HISTFILE special case  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [HACKERS] psql 'none' as a HISTFILE special case
List pgsql-patches
On 8/21/06, Bruce Momjian <bruce@momjian.us> wrote:
> Tom Lane wrote:
> > Neil Conway <neilc@samurai.com> writes:
> > > On Mon, 2006-08-21 at 19:27 +0300, Martin Atukunda wrote:
> > >> If readline is used by psql, a history file is automatically used.
> > >> This patch adds the special file name 'none', which if set as the
> > >> HISTFILE parameter, will cause psql not to use the history file.
> >
> > > I think it would be cleaner to use a separate \set variable to control
> > > whether a history file is written, rather than needlessly overloading
> > > the meaning of HISTFILE.
> >
> > Why is this useful at all?  There's already the -n (don't use readline)
> > switch.
>
> Seems he wants readline without history, perhaps for security.  Doesn't
> setting HISTFILE to /dev/null work?
>
hmm, setting HISTFILE to /dev/null doesn't work on my MacOSX here. so
I whipped up this patch.

- Martin -

pgsql-patches by date:

Previous
From: Böszörményi Zoltán
Date:
Subject: Re: [HACKERS] Performance testing of COPY (SELECT) TO
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] psql 'none' as a HISTFILE special case