-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sql: inserted data appears not being inserted after all #4660
Comments
multi-node? Are you doing the finals |
Nope, all on the same server, only 1 node in "cluster" |
Clarification: if I run the same test using the CLI client with |
How to reproduce:
You can also compare against Postgres by setting jdbc-mode to |
As suggested by @andreimatei I changed the test to: create table mono (val int, sts bigint, node int, tb int)
insert into mono (val, sts, node, tb) values (-1, 0, -1, -1)
-- do 10 times:
begin
v := select max(val) from mono
select * from mono where val = v
n := select now()
insert into mono (val, sts, node, tb) values (1 + v, n, 0, 0)
select * from mono --- THIS IS NEW
commit
-- then at the end:
begin
v := select max(val) from mono -- NEW
select * from mono where val = v -- NEW
n := select now() -- NEW
insert into mono (val, sts, node, tb) values (1 + v, n, 0, 0) -- NEW
select * from mono -- as previously
commit During the loop I see the table growing as a result of What is different between the last transactions and the 10 transactions before? There's a pause of 2 seconds between the end of the loop and the last transaction. Perhaps this pause is sufficient to trigger #4656? |
(all this while looking at #4036 ) |
Cannot reproduce the error after upgrading to the latest master revision. |
So here's the scenario:
the INSERTs appear to work properly because I see
v
increase in value during the loop.However the final SELECT always returns an empty set. I also observe an empty table if I query it from another client while this test is running.
Full network trace attached: error.txt
Client and server running on same machine. You can see that all statements are first prepared and that insert uses RETURNING. Not sure that's relevant.
The text was updated successfully, but these errors were encountered: