BUG #1742: long tables can NOT be updated via "rcv:menu" or sql command line - Mailing list pgsql-bugs

From Wade Zhang
Subject BUG #1742: long tables can NOT be updated via "rcv:menu" or sql command line
Date
Msg-id 20050701093453.D5F27F0B13@svr2.postgresql.org
Whole thread Raw
List pgsql-bugs
The following bug has been logged online:

Bug reference:      1742
Logged by:          Wade Zhang
Email address:      wxzhang@lucent.com
PostgreSQL version: on MAS n440aa1
Operating system:   SUN solaris
Description:        long tables can NOT be updated via "rcv:menu" or sql
command line
Details:

Now we encountered a problem that database can not be updated from
rcv:menu,spa form or PostgreSQL command line if the table length exceeds a
threshold, we are not sure the real value of this threshold.
In summary, a short record can be updated correctly, and a long record
update always failed with error message "No Tuples Found".
I am afraid that there is a lenght limit on PostgreSQL interface.
However, the database can be updated correctly via an executable .sql file,
with header of "psql -h pglocalhost -U scncraft <<!eof" and end of "COMMIT;
!eof".

The MAS lab in use is N440AA1, you can try to verify the above issues.
rcv:menu,spa->100->3
(1) a short table, Discount_Plan_tbl (the number is 30), can be updated
correctly.
(2) a long table, Counter_Definition_tbl (the number is 16), can NOT be
updated, and failed with "No Tuples Found".
And you can also try any other tables with length of more than 48
records(three pages display) and less than 32 pages(two pages display).
All the short tables can be updated and long tables can NOT.

Furthermroe, all these tables can be updated via an executable .sql file.

We guest the database interface via "rcv:menu,spa" is not implemented
properly.

Hope DB team can fix it as soon as possbile since such a problem blocked the
whole testing work of the whole project.

pgsql-bugs by date:

Previous
From:
Date:
Subject: server restart when connections thread over 155 in PostgreSQL 8.03
Next
From: Michael Fuhr
Date:
Subject: Re: BUG #1735: row number -1 is out of range 0..-1 error