Обсуждение: Cursor keys not working, repost.

Hi I'm still having problem with my cursors working in psql connecting to
postgresql v7.1 server.

I have this problem on Linux Mandrake v7.1, v7.2, Linux Redhat v6.2, v7.1.

I have installed all the header files from:

/usr/src/redhat/SOURCES/readline-2.2.1 temporarily into
/usr/local/include.

My configure line is:

./configure --with-includes="/usr/local/include"

Extract from config.log:

configure:3143: checking for readline
configure:3192: checking for library containing using_history
configure:4752: checking for readline/readline.h
configure:4752: checking for readline.h
configure:4792: checking for readline/history.h
configure:4792: checking for history.h

Extract from 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='no'}
ac_cv_header_readline_readline_h=${ac_cv_header_readline_readline_h='no'}

I don't know what else to do, I appear to be doing everything correctly as
far as I know, and I am frustrated no one else has this problem, but yet I
do on 4 different systems?

The cursor keys have worked in previous versions UP to v7.1 but what has
changed now that they don't? I definately haven't changed anything on all
the systems...

Please help :)

Thankyou.

Grant <grant@conprojan.com.au> writes:
> I have installed all the header files from:
> /usr/src/redhat/SOURCES/readline-2.2.1 temporarily into
> /usr/local/include.

(1) Did you remove config.cache and rerun configure after installing the
headers?  Maybe your problem is just that configure is caching the
not-found result ...

(2) readline 2.2.1 is really ancient; the current release is 4.2.
I'm not certain that we'd work with 2.2.1 even if you got past the
configure issue.  You might need to update to a newer readline
library.  (Caution: readline 4.2 is so new that PG 7.1 doesn't talk
to it.  Recommended combination is rl 4.1 with PG 7.1, or rl 4.2
with PG >= 7.1.1.)

            regards, tom lane

> (1) Did you remove config.cache and rerun configure after installing the
> headers?  Maybe your problem is just that configure is caching the
> not-found result ...

Yes I did remove config.cache, this was not the problem see below.

> (2) readline 2.2.1 is really ancient; the current release is 4.2.
> I'm not certain that we'd work with 2.2.1 even if you got past the
> configure issue.  You might need to update to a newer readline
> library.  (Caution: readline 4.2 is so new that PG 7.1 doesn't talk
> to it.  Recommended combination is rl 4.1 with PG 7.1, or rl 4.2
> with PG >= 7.1.1.)

I have managed to get the cursors working with readline-4.1.tar.gz. I have
one question and one suggestion.

1. Is it documented that readline-4.1 is a requirement for postgresql v7.1
in order to use the cursors?

2. Can the below steps be placed in the FAQ as I'm sure I was not the only
person who had/has this problem.

01. wget ftp://sunsite.cnlab-switch.ch/mirror/stampede/unstable/pre-0.90/clean-source/base/readline-4.1.tar.gz

02. rpm -e --nodeps `rpm -qa | grep readline`

03. tar -zxf readline-4.1.tar.gz

04. cd readline-4.1

05. ./configure

06. make

07. make install

08. make install-headers

09. mv readline-4.1 /usr/local/src

10. Make sure sure /usr/local/include is in /etc/ld.so.conf and re-run
/sbin/ldconfig. Then continue on with your postgresql configuration
and installation, making sure you stop any currently running
postgresql processes before `make install`.

Thanks for your time Tom.

Grant <grant@conprojan.com.au> writes:
> 1. Is it documented that readline-4.1 is a requirement for postgresql v7.1
> in order to use the cursors?

No, because it isn't a requirement; we do work with older readline
versions, I'm just not sure how far back.  I know I have functional
editing and history on an old RedHat box that has readline 3.0.
If anyone wants to research readline 2.* and figure out where the
compatibility boundary is, we could certainly put that into the docs ...

            regards, tom lane

pg_dump failed with message

getTables(): SELECT (for VIEW DEFINITION) failed.
Explanation from backend: ERROR:  cache lookup for proc 372947 failed

Where I should dig?
Thanx.

--
Best regards,
 Leonid                            mailto:leo@rusmedia.net

Leonid <leo@rusmedia.net> writes:
> pg_dump failed with message
> getTables(): SELECT (for VIEW DEFINITION) failed.
> Explanation from backend: ERROR:  cache lookup for proc 372947 failed

> Where I should dig?

You have a view that refers to a function that no longer exists.

Philip: seems like it would be helpful if this pg_dump message mentioned
*which* viewname it was failing on.  There are other cases where more
info could be reported, too...

            regards, tom lane