[Info-ingres] x100 transaction
Martin Bowes
martin.bowes at ndph.ox.ac.uk
Tue May 11 10:09:43 UTC 2021
Hi Karl,
> What's going on is that the delay_txn_start config parameter is probably set to ON.
Yes.
> That tells the DBMS server to not bother starting an X100 transaction when an Ingres transaction starts, unless something x100-y is being done. The initial drop table doesn't force an x100 transaction start because there's no x100 work to do. The create table does an explicit check to see if it's in an Ingres transaction but no x100 transaction and throws that error.
Seems fair.
> Once X100 tables exist, the check is a little different and you don't get the error.
Whoa! An initialisation condition.
So starting with an empty database...
The drop table if exists / create table with structure = x100 fails as before.
However, if we ensure we have at least one existing x100 table first...:
create table dummy(id integer4 not null not default) with structure = x100;
commit;
drop table if exists base;
create table base(id integer4 not null not default) with structure = x100;
commit;
That now works as expected.
Marty
_______________________________________________
Info-ingres mailing list
Info-ingres at lists.planetingres.org
https://lists.planetingres.org/mailman/listinfo/info-ingres
More information about the Info-ingres
mailing list