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

From Bruce Momjian
Subject Re: psql 'none' as a HISTFILE special case
Date
Msg-id 200608211653.k7LGrAw27676@momjian.us
Whole thread Raw
In response to Re: psql 'none' as a HISTFILE special case  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: psql 'none' as a HISTFILE special case  ("Martin Atukunda" <matlads@gmail.com>)
List pgsql-patches
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?

--
  Bruce Momjian   bruce@momjian.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: psql 'none' as a HISTFILE special case
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] proposal - plpgsql: execute using into