| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org, Neil Conway <neilc(at)samurai(dot)com> |
| Cc: | 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:51:50 |
| Message-ID: | 23697.1156179110@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-08-21 16:53:10 | Re: psql 'none' as a HISTFILE special case |
| Previous Message | Tom Lane | 2006-08-21 16:46:04 | Re: [PATCHES] [PATCH] Provide 8-byte transaction IDs to |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-08-21 16:53:10 | Re: psql 'none' as a HISTFILE special case |
| Previous Message | Tom Lane | 2006-08-21 16:46:04 | Re: [PATCHES] [PATCH] Provide 8-byte transaction IDs to |