dpage
commented
8 years ago Comment migrated from Redmine: https://redmine.postgresql.org/issues/1854#note-1 Originally created by Jan Kort at 2016-10-13 07:31:31 UTC.
Apparently pressing F5 20 times is not enough, it has to be at least 30 times.
Also, I misprinted the error message (I was confused because there was no newline in it), it really says:
Cursor could not be found for the async connection.
Now I read it it makes more sense like that.
Here is also what "About pgadmin 4" says if that helps:
Version 1.0 Copyright Copyright 2013 - 2016, The pgAdmin Development Team Python Version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015, 20:40:30) [MSC v.1500 64 bit (AMD64)] Flask Version 0.11.1 Application Mode Desktop Current User pgadmin4@pgadmin.org
Issue migrated from Redmine: https://redmine.postgresql.org/issues/1854 Originally created by Jan Kort at 2016-10-12 21:45:54 UTC.
This is a bug report for pgadmin4 I cannot reproduce the original error in a simple example. But by trying to reproduce it I found another bug that I can reproduce using these steps: -- Execute (F5) the first 3 lines of this script once DROP TABLE IF EXISTS TEST_JAN; CREATE TABLE TEST_JAN (F1 TEXT); INSERT INTO TEST_JAN (F1) VALUES ('Test'); -- Execute (F5) the next line 20-30 times really fast, causes loop saying: connection.Cursor could not be found for the async INSERT INTO TEST_JAN (SELECT FROM TEST_JAN); -- Execute (F5) the next line shows 4096 records inserted SELECT COUNT() FROM TEST_JAN; -- Other issues: -- 1. executing trivial queries take 400ms or more, used to be 15ms -- 2. I was trying to reproduce another issue with this example, but I can't. -- The other issues was that sometimes the progres of the "Query Tool" keeps on going -- eventhough the query is quick enough. When I restart the querytool, the exact same -- query executes fine (400ms). This happens maybe 1 in 20 times, but not with simple -- examples, so I dont know..