Re: [HACKERS] [PATCHES] psql 'none' as a HISTFILE special case

2006-08-25 Thread Martin Atukunda
On 8/25/06, Tom Lane <[EMAIL PROTECTED]> wrote: "Martin Atukunda" <[EMAIL PROTECTED]> writes: > On 8/25/06, Tom Lane <[EMAIL PROTECTED]> wrote: >> There's probably no way to get Apple's libedit to not try the fchmod, >> so what do we want to do here? Maybe special-case the string >> "/dev/null"?

Re: [HACKERS] [PATCHES] psql 'none' as a HISTFILE special case

2006-08-25 Thread Tom Lane
"Martin Atukunda" <[EMAIL PROTECTED]> writes: > On 8/25/06, Tom Lane <[EMAIL PROTECTED]> wrote: >> There's probably no way to get Apple's libedit to not try the fchmod, >> so what do we want to do here? Maybe special-case the string >> "/dev/null"? > If this is OK, I can up with a patch that spec

Re: [HACKERS] [PATCHES] psql 'none' as a HISTFILE special case

2006-08-25 Thread Martin Atukunda
On 8/25/06, Tom Lane <[EMAIL PROTECTED]> wrote: > When I set HISTFILE to /dev/null I get the following: > could not save history to file "/dev/null": Operation not permitted Hm. ktrace shows this happening: 23279 psql CALL open(0x302d70,0x601,0x1b6) 23279 psql NAMI "/dev/null" 232

Re: [HACKERS] [PATCHES] psql 'none' as a HISTFILE special case

2006-08-25 Thread Tom Lane
"Martin Atukunda" <[EMAIL PROTECTED]> writes: > On 8/25/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote: >> Please elaborate on "doesn't work". > without any .psqlrc file I get the following error when quitting a psql > session: > could not save history to file "/Users/matlads/.psql_history": Inva

Re: [HACKERS] [PATCHES] psql 'none' as a HISTFILE special case

2006-08-25 Thread Martin Atukunda
On 8/25/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote: Am Freitag, 25. August 2006 17:03 schrieb Martin Atukunda: > hmm, setting HISTFILE to /dev/null doesn't work on my MacOSX here. Please elaborate on "doesn't work". without any .psqlrc file I get the following error when quitting a psql s

Re: [HACKERS] [PATCHES] psql 'none' as a HISTFILE special case

2006-08-25 Thread Peter Eisentraut
Am Freitag, 25. August 2006 17:03 schrieb Martin Atukunda: > hmm, setting HISTFILE to /dev/null doesn't work on my MacOSX here. Please elaborate on "doesn't work". -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)-

Re: [PATCHES] psql 'none' as a HISTFILE special case

2006-08-25 Thread Martin Atukunda
On 8/21/06, Bruce Momjian <[EMAIL PROTECTED]> wrote: Tom Lane wrote: > Neil Conway <[EMAIL PROTECTED]> 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', w

Re: [PATCHES] psql 'none' as a HISTFILE special case

2006-08-21 Thread Bruce Momjian
Tom Lane wrote: > Neil Conway <[EMAIL PROTECTED]> 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

Re: [PATCHES] psql 'none' as a HISTFILE special case

2006-08-21 Thread Tom Lane
Neil Conway <[EMAIL PROTECTED]> 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 histor

Re: [PATCHES] psql 'none' as a HISTFILE special case

2006-08-21 Thread Neil Conway
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

[PATCHES] psql 'none' as a HISTFILE special case

2006-08-21 Thread Martin Atukunda
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. - Martin - psql_allow_none_as_HISTFILE.diff Description: Binary data ---