Re: psql 'none' as a HISTFILE special case

From: "Martin Atukunda" <matlads(at)gmail(dot)com>
To: "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org
Subject: Re: psql 'none' as a HISTFILE special case
Date: 2006-08-25 15:03:55
Message-ID: ce92d7150608250803x7861d577ob50a40ff5625ab46@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On 8/21/06, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Tom Lane wrote:
> > Neil Conway <neilc(at)samurai(dot)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 -

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2006-08-25 15:06:50 Re: Tricky bugs in concurrent index build
Previous Message Tom Lane 2006-08-25 14:58:27 Re: Tricky bugs in concurrent index build

Browse pgsql-patches by date

  From Date Subject
Next Message Peter Eisentraut 2006-08-25 15:17:25 Re: [HACKERS] psql 'none' as a HISTFILE special case
Previous Message Böszörményi Zoltán 2006-08-25 14:18:42 Re: Performance testing of COPY (SELECT) TO