| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Neil Conway <neilc(at)samurai(dot)com>, Martin Atukunda <matlads(at)gmail(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: psql 'none' as a HISTFILE special case |
| Date: | 2006-08-21 16:53:10 |
| Message-ID: | 200608211653.k7LGrAw27676@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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?
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manuel A. Fernandez Montecelo | 2006-08-21 16:59:56 | Re: BUG #2585: Please provide pkg-config support |
| Previous Message | Tom Lane | 2006-08-21 16:51:50 | Re: psql 'none' as a HISTFILE special case |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2006-08-21 17:15:43 | Re: [PATCHES] [PATCH] Provide 8-byte transaction IDs to |
| Previous Message | Tom Lane | 2006-08-21 16:51:50 | Re: psql 'none' as a HISTFILE special case |