Skip to content
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

Hang when database with disconnect trigger using MON$ tables is shutting down #7979

Closed
AlexPeshkoff opened this issue Jan 26, 2024 · 1 comment

Comments

@AlexPeshkoff
Copy link
Member

When the following database:

SET SQL DIALECT 3;

CREATE TABLE LOGGER (DET_TIME TIMESTAMP,
AC INTEGER);

SET TERM ^ ;
CREATE TRIGGER LOGGER
ACTIVE ON DISCONNECT POSITION 0
as declare variable c int; begin select count(*) from mon$attachments into :c; insert into logger values(current_timestamp, :c); end ^
SET TERM ; ^

COMMIT WORK;

having at least one additional attachment is shutdown SS hangs.

@AlexPeshkoff AlexPeshkoff self-assigned this Jan 26, 2024
@AlexPeshkoff AlexPeshkoff changed the title Hang when database with disconnect trigger using MON$ tables shutdown Hang when database with disconnect trigger using MON$ tables is shutting down Jan 28, 2024
@AlexPeshkoff AlexPeshkoff reopened this Jan 28, 2024
@pavel-zotov
Copy link

@@@ QA issue @@@

Bug could NOT be reproduced on Windows.
Bug can be reproduced only when appropriate code runs OUTSIDE current firebird-QA framework, i.e. directly from OS.
Because of that, test creates temporary .py script which is launched further using subprocess.run( [ sys.executable ...] ).
Confirmed problem on 6.0.0.219: 'gfix -shut full -force 0' hangs.
Checked on 6.0.0.244.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment