Re: [Firebird-devel] Start transaction from base transaction

[Vlad Khorsun]

19.02.2019 18:24, Adriano dos Santos Fernandes wrote:

Hi Vlad,

I restarted work on this feature now using commit numbers.


  Good to know. Could you publish user interface before it is too late ? ;)


Initial prototype seems to work easily.


  It should be not too hard, agree


So now with current master code, is it ok to have transaction numbers
TN1 < TN2 < TN3 with their correspondents tra_snapshot_number not being
TSN1 <= TSN2 <= TSN3 ?


  Yes. More, RC transactions have no tra_snapshot_number (as you know of 
course).


That is, when TN3 starts it's tra_snapshot_number will not be the latest
commit number if that transaction is going to share another transaction
snapshot, but say the same tra_snapshot_number of TN1 even if TN2 was
already committed.

Does that break any assumption on Firebird transaction or GC architecture?


  As i understand you - it doen't break anything. For me, it is safe to assign
to the new snapshot (CONCURRENCY) transaction number of already existing and
still alive snapshot. It is very important to ensure existence of that snapshot
number until assignment happens (and new snapshot slot allocated).

Regards,
Vlad


Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Re: [Firebird-devel] Start transaction from base transaction

[Adriano dos Santos Fernandes]

Hi Vlad,

I restarted work on this feature now using commit numbers.

Initial prototype seems to work easily.

So now with current master code, is it ok to have transaction numbers
TN1 < TN2 < TN3 with their correspondents tra_snapshot_number not being
TSN1 <= TSN2 <= TSN3 ?

That is, when TN3 starts it's tra_snapshot_number will not be the latest
commit number if that transaction is going to share another transaction
snapshot, but say the same tra_snapshot_number of TN1 even if TN2 was
already committed.

Does that break any assumption on Firebird transaction or GC architecture?


Adriano



Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-6006) if fb4 is not in dir /opt/firebird/ libtomcrypt.so.1 => not found

[Segey Khalyutin (JIRA)]

if fb4 is not in  dir /opt/firebird/libtomcrypt.so.1 => not found 
--

 Key: CORE-6006
 URL: http://tracker.firebirdsql.org/browse/CORE-6006
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 4.0 Alpha 1
 Environment: openSUSE Leap-15 x64
Firebird TCP/IP server version LI-T4.0.0.1376 Firebird 4.0 Alpha 1

Reporter: Segey Khalyutin
Priority: Trivial


if fb4 is not in  dir /opt/firebird/libtomcrypt.so.1 => not found 

when  /opt/firebird_4/ renamed to /opt/firebird/ starting is ok  


ost:~ # systemctl status firebird-4
Warning: firebird-4.service changed on disk. Run 'systemctl daemon-reload' to 
reload units.
? firebird-4.service - Firebird Database Server 4.0.a
   Loaded: loaded (/opt/firebird_4/misc/firebird-4.service; linked; vendor 
preset: disabled)
   Active: failed (Result: exit-code) since Tue 2019-02-19 16:12:11 EET; 17s ago
  Process: 9302 ExecStart=/opt/firebird_4/bin/fbguard -pidfile 
/var/run/firebird/firebird_4.pid -daemon -forever (code=exited, stat>

Feb 19 16:12:11 host systemd[1]: Starting Firebird Database Server 4.0.a...
Feb 19 16:12:11 host fbguard[9302]: /opt/firebird_4/bin/fbguard: error while 
loading shared libraries: libtomcrypt.so.1: cannot ope>
Feb 19 16:12:11 host systemd[1]: firebird-4.service: Control process exited, 
code=exited status=127
Feb 19 16:12:11 host systemd[1]: Failed to start Firebird Database Server 4.0.a.
Feb 19 16:12:11 host systemd[1]: firebird-4.service: Unit entered failed state.
Feb 19 16:12:11 host systemd[1]: firebird-4.service: Failed with result 
'exit-code'.


or bug reporting instructions, please see:
.
host:~ # ldd /opt/firebird_4/bin/fbguard
linux-vdso.so.1 (0x749ec000)
libfbclient.so.2 => /opt/firebird_4/bin/../lib/libfbclient.so.2 
(0x7f7fe3a5c000)
libtommath.so.0 => /usr/lib64/libtommath.so.0 (0x7f7fe3842000)
libtomcrypt.so.1 => not found
libdl.so.2 => /lib64/libdl.so.2 (0x7f7fe363e000)
libncurses.so.5 => /lib64/libncurses.so.5 (0x7f7fe3415000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x7f7fe308b000)
libm.so.6 => /lib64/libm.so.6 (0x7f7fe2d4)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7f7fe2b28000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x7f7fe290a000)
libc.so.6 => /lib64/libc.so.6 (0x7f7fe255)
/lib64/ld-linux-x86-64.so.2 (0x7f7fe3e8b000)
libtomcrypt.so.1 => not found
libtinfo.so.6 => /lib64/libtinfo.so.6 (0x7f7fe2322000)
host:~ # locate libtomcrypt
/opt/firebird_4/lib/.tm/libtomcrypt.so
/opt/firebird_4/lib/.tm/libtomcrypt.so.1
/opt/firebird_4/lib/.tm/libtomcrypt.so.1.0.1
/usr/lib64/libtomcrypt.so
/usr/lib64/libtomcrypt.so.1
/usr/lib64/libtomcrypt.so.1.0.1


-- 
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-6005) Multiple records UPDATE overwrite TIGGERS modification in the same table.

[JIRA]

Multiple records UPDATE overwrite TIGGERS modification in the same table.
-

 Key: CORE-6005
 URL: http://tracker.firebirdsql.org/browse/CORE-6005
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.4
Reporter: Javier Fernández Castillejo
Priority: Critical


CREATE TABLE TEST_UPDATE 
(
  ID  INTEGER NOT NULL,
  FIELD1  INTEGER,
  FIELD2  INTEGER,
 CONSTRAINT PK_TEST_UPDATE PRIMARY KEY (ID)
);

SET TERM ^^ ;
CREATE TRIGGER TEST_UPDATE_AU FOR TEST_UPDATE ACTIVE AFTER UPDATE POSITION 0 AS
begin
  Update TEST_UPDATE
SET FIELD2=NEW.FIELD1
Where ID=NEW.ID+1;
end ^^
SET TERM ; ^^

Insert into TEST_UPDATE (ID,FIELD1,FIELD2) VALUES (1,0,0);
Insert into TEST_UPDATE (ID,FIELD1,FIELD2) VALUES (2,0,0);
Insert into TEST_UPDATE (ID,FIELD1,FIELD2) VALUES (3,0,0);
Insert into TEST_UPDATE (ID,FIELD1,FIELD2) VALUES (4,0,0);
Insert into TEST_UPDATE (ID,FIELD1,FIELD2) VALUES (5,0,0);

Update TEST_UPDATE
Set Field1=10
Where ID in (2,3);

=== In Firebird 3.0.4 ===
Select *
From TEST_UPDATE;

ID,FIELD1,FIELD2
1,0,0
2,10,0
3,10,0 <== This value must be 10
4,0,10
5,0,0

In Firebird 2.5 is Correct
ID,FIELD1,FIELD2
1,0,0
2,10,0
3,10,10
4,0,10
5,0,0


-- 
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] Dropping identity

[Jiří Činčura]

Hi *,

can I drop identity specification from the column on FB3? I've found only 
CORE-5431, but that's only for 4.0.

-- 
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/


Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-6004) Add a configuration switch to disable the "TCP Loopback Fast Path" option (Windows only)

[KS (JIRA)]

Add a configuration switch to disable the "TCP Loopback Fast Path" option 
(Windows only)


 Key: CORE-6004
 URL: http://tracker.firebirdsql.org/browse/CORE-6004
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Affects Versions: 3.0.4
 Environment: Windows 8/2012 and higher
Reporter: KS


We recently ran into a problem with the "TCP Loopback Fast Path" option 
(introduced with CORE-4563).

Having a Windows 2016 Server (as a guest OS using VMWare) newly booted, any 
already established local TCP connections are broken in the moment the 
(optional) "Remote Access Management Service" Windows service starts up. This 
affects only local TCP connections having the Fast Path option enabled. For 
Firebird, this results in errors like "ISC ERROR MESSAGE: Error writing data to 
the connection". After reestablishing the connection all works fine and doesn't 
break again. I verified that this issue doesn't occur when the Fast Path option 
isn't used. I don't think that this a problem in Firebird, because other 
loopback TCP connections between different system components (other than 
Firebird) that make use of the Fast Path option were affected in the same way.

As the Fast Path option is generally desirable but may cause problems under 
some rare conditions, I think it favourable to have a config switch allowing to 
disable it. It's sufficient to have this switch on the server side, because the 
Fast Path option will only become active if both sides (client + server) opt in 
for it.

Here's my proposal for a new Firebird.conf section (to be added after " 
#TcpNoNagle = 1"):

#
# Either enables or disables the "TCP Loopback Fast Path" feature 
(SIO_LOOPBACK_FAST_PATH).
# Applies to Windows (version 8/2012 or higher) only.
#
# Type: Boolean, default 1 (true)
#
#TcpLoopbackFastPathOption = 1



-- 
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