My previous question (why decrease performance on FB in 3-4 days) generate my next question...

I see, that the oldest and next transaction's distance increase so the oldest remain the staring value.

I wrote a test app.

CREATE TABLE "TEST"
(
"X" INTEGER NOT NULL,
"Y" VARCHAR(200) CHARACTER SET WIN1250 NOT NULL,
CONSTRAINT "PK_TEST" PRIMARY KEY ("X")

Simple table...

I create a thread, which create an SQL session, and insert rows to table with starttransaction and commit to all insert
continuously.
Then, "next transaction" increace continuously, and the OAT remain on start vaule. The sweep set to OAT to Next transaction. This is
correct (i think)

After that i create a new session, which start transaction, and SELECT from TEST table and commit. From this time on the OAT remain
on initial value, and the sweep cannot "clean" this.

My question: how i create app, where a thread insert rows to a table, and another read from this. As i see, in this case the OAT
never change (except if i restart my app).

I not use commitretain.

Balázs Szakály
szakalyb@...