[Firebird-devel] [FB-Tracker] Created: (CORE-5942) Async write for security#.fdb as default
Async write for security#.fdb as default Key: CORE-5942 URL: http://tracker.firebirdsql.org/browse/CORE-5942 Project: Firebird Core Issue Type: Improvement Components: Installation Reporter: Basil A. Sidorov Priority: Minor Make write asinc for security#.fdb as default option. Motivation: lowered IO-load for environment with many short-lived connections. Workaround: change attribute manualy via two restart Firebird server. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] [FB-Tracker] Created: (CORE-5941) Altering non existing trigger with OLD. variable cause "Column unknown" instead "Trigger not found"
Altering non existing trigger with OLD. variable cause "Column unknown" instead "Trigger not found" --- Key: CORE-5941 URL: http://tracker.firebirdsql.org/browse/CORE-5941 Project: Firebird Core Issue Type: Bug Components: Engine Affects Versions: 3.0.4, 3.0.5 Reporter: Karol Bieniaszewski try altering not existing trigger SET TERM ^ ; ALTER TRIGGER XYZXX ACTIVE AFTER DELETE POSITION 1000 AS DECLARE VARIABLE VAR_OLD_UMOWA_ID CHAR(7); begin END^ SET TERM ; ^ as expected: Engine Code: 335544351 Engine Message : unsuccessful metadata update ALTER TRIGGER XYZXX failed Trigger XYZXX not found add reference to OLD variable in the not existing trigger SET TERM ^ ; ALTER TRIGGER XYZXX ACTIVE AFTER DELETE POSITION 1000 AS DECLARE VARIABLE VAR_OLD_UMOWA_ID CHAR(7); begin VAR_OLD_UMOWA_ID = OLD.UMOWA_ID; END^ SET TERM ; ^ Engine Code: 335544351 Engine Message : unsuccessful metadata update ALTER TRIGGER XYZXX failed Dynamic SQL Error SQL error code = -206 Column unknown OLD.UMOWA_ID but the main reason is that this trigger does not exists at all the body does not matter here -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Meltdown and Spectre
Hi Gábor! df -Th | grep ram tmpfs tmpfs 15G 820M 15G 6% /ramdisk András -Original Message- From: Gabor Boros Sent: Sunday, October 14, 2018 10:26 AM To: firebird-devel@lists.sourceforge.net Subject: Re: [Firebird-devel] Meltdown and Spectre 2018. 01. 09. 10:52 keltezéssel, Omacht András írta: > The database file and the tmp directory located on ramdisk. What was the filesystem of the ramdisk? Tmpfs? Gabor Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel __ Information from ESET Mail Security, version of virus signature database 18211 (20181014) __ The message was checked by ESET Mail Security. http://www.eset.com __ Information from ESET Mail Security, version of virus signature database 18216 (20181015) __ The message was checked by ESET Mail Security. http://www.eset.com Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
