RE: One last thing... psql and readline

I've got the same problem with readline and psql using 7.0 RC1.

I found that there was something odd when ran configure.  Here's the
readline stuff I grepped out of config.cache:

  ac_cv_header_readline_h=${ac_cv_header_readline_h='no'}
  ac_cv_header_readline_history_h=${ac_cv_header_readline_history_h='yes'}
  ac_cv_header_readline_readline_h=${ac_cv_header_readline_readline_h='yes'}
  ac_cv_lib_readline_main=${ac_cv_lib_readline_main='yes'}
  ac_cv_lib_readline_using_history=${ac_cv_lib_readline_using_history='yes'}

Notice that the first line still says "no".  Looks to me like it wants to
find readline.h in /usr/include, as well as, /usr/include/readline.  Could
this be the source of the problem?

-=michael=-

*****************************************************
*  Michael S. Kelly
*  4800 SW Griffith Dr., Ste. 202
*  Beaverton, OR  97005 USA
*  voice: (503)644-6106 x122  fax: (503)643-8425
*  <michaelk@axian.com>
*  http://www.axian.com/
*****************************************************
*    Axian:  Software Consulting and Training
*****************************************************


-----Original Message-----
From: Steve Wolfe [mailto:steve@iboats.com]
Sent: Thursday, April 20, 2000 9:51 AM
To: pgsql-general@postgresql.org
Subject: One last thing... psql and readline



  One last problem - after upgrading to 6.5.3, psql no longer seems to be
using the readline stuff for going through the command history, all we get
are the funky control characters ("^[[A^[[A", etc.)  Any info on how to
make it work?

  Oh, yes, it seems like 6.5.3 is more strict about not allowing you to use
reserved words for field names.  Some nimrod had created a table with field
names 'time' and 'date', boy, did that make trying to restore fun, fun,
fun.....

steve