Bruce Momjian wrote:
Here is what you can do:
SELECT filename,
(SELECT file_len FROM pg_file_stat(filename)),
(SELECT file_ctime FROM pg_file_stat(filename)),
(SELECT file_mtime FROM pg_file_stat(filename)),
(SELECT file_atime FROM pg_file_stat(filename))
FROM pg_dir_ls('/etc') AS
Hmm. And this is a cvs pull that was before Bruce actually disabled
readline? What locale are you in?
Actually, I just just typed away in the bash shell, which
uses readline as well.
Ok, then we're testing completely different things. I'm talking about
the psql client when running under
Magnus Hagander wrote:
Ok, then we're testing completely different things. I'm talking about
the psql client when running under CMD.EXE, *not* in the msys shell.
(backslash works fine in the bash shell)
OK, I'll try that later. As an additional data point, running sh.exe
from within cmd.exe
Ok, here is another one.
Doc patches coming up if/when this one is approved.
//Magnus
+ /* Kerberos methods not listed because they are not supported
+* over local connections and are rejected in hba.c */
Is this true of all local connections, or only Unix socket
Magnus Hagander wrote:
Just for reference, what features are we losing without readline. Tab
completion, but what more?
Command history, customizable key bindings, cut and paste, cursor keys
come to mind.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Peter Eisentraut wrote:
Magnus Hagander wrote:
Ok, here is another one.
Doc patches coming up if/when this one is approved.
I think this warning is seriously going to annoy me. Can we do without
it?
What if we skip the warning if the user specifically asks for 'trust'?
Would that
