[Firebird-devel] [FB-Tracker] Created: (CORE-6542) Implementation of SUBSTRING for multi-byte character sets is inefficient

[Vlad Khorsun (JIRA)]

Implementation of SUBSTRING for multi-byte character sets is inefficient 
-

 Key: CORE-6542
 URL: http://tracker.firebirdsql.org/browse/CORE-6542
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Affects Versions: 4.0 RC 1, 3.0.7
Reporter: Vlad Khorsun


The case below shows bad performance of SUBSTRING for UTF8 comparing with 
(legacy) UNICODE_FSS 

a) UNICODE_FSS

execute block
as
declare str1 varchar(8000) character set unicode_fss;
declare str2 varchar(10)   character set unicode_fss;
declare n int = 10;
begin
  str1 = LPAD('abcd', 8000, '--');
  while (n > 0) do
  begin
str2 = SUBSTRING(str1 from 1 FOR 10);
n = n - 1;
  end
end

Execute time = 62ms


b) UTF8

execute block
as
declare str1 varchar(8000) character set utf8;
declare str2 varchar(10)   character set utf8;
declare n int = 10;
begin
  str1 = LPAD('abcd', 8000, '--');
  while (n > 0) do
  begin
str2 = SUBSTRING(str1 from 1 FOR 10);
n = n - 1;
  end
end

Execute time = 983ms

The case is simplified and based on end-user report. In user case the same 
query on the system tables run much longer with FB4 than with FB3
(test database was restored from the same backup). Origin of the problem is 
that FB4 uses UTF8 for metadata while FB3 uses UNICODE_FSS.

The SUBSTRING implementation for UNICODE_FSS (internal_fss_substring()) is 
straigthforward and logical - it skips POSITION characters
from the start of the source string first and then copy LENGTH chars into dest 
string.

The UTF8 implementation (MultiByteCharSet::substring()) convert whole source 
string into UTF16 and only then get substring of UTF16 string. 
This is simple but very inefficient especially for a long strings and small 
POSITION values.


-- 
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-6526) AV in engine when StatementTimeout is active for user statement and some internal DSQL statement was executed as part of overall execution process

[Vlad Khorsun (JIRA)]

AV in engine when StatementTimeout is active for user statement and some 
internal DSQL statement was executed as part of overall execution process
--

 Key: CORE-6526
 URL: http://tracker.firebirdsql.org/browse/CORE-6526
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 4.0 RC 1, 4.0 Beta 2, 4.0 Beta 1
Reporter: Vlad Khorsun


In the case below the internal DSQL statement is run on commit when index is 
modified.
Note, most internal statements used by the engine is ESQL, not DSQL - thus they 
are not interact with StatementTImeout.


set term ^;

execute block as begin
  in autonomous transaction do
 execute statement 'set statistics index rdb$index_0';
end
^
set statement timeout 60
^
execute block as begin
  in autonomous transaction do
 execute statement 'set statistics index rdb$index_0';
end
^

Statement failed, SQLSTATE = 08006
Error reading data from the connection.


The bug was reported by Pavel Zotov with much more complex scenario.


-- 
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-6488) Event delivery could be missed when local (XNET) protocol is used

[Vlad Khorsun (JIRA)]

Event delivery could be missed when local (XNET) protocol is used
-

 Key: CORE-6488
 URL: http://tracker.firebirdsql.org/browse/CORE-6488
 Project: Firebird Core
  Issue Type: Bug
  Components: API / Client Library, Engine
Affects Versions: 4.0 RC 1, 3.0.7, 2.5.9
 Environment: Windows only
Reporter: Vlad Khorsun


The bug was reported at https://www.sql.ru/forum/165/

The problem could happen when:
- the op_event packet is longer than the XNET transmission buffer length (100 
bytes), and 
- client start to read data a bit later than server write first 100 bytes.

In this case race between writer and reader could happen and reader could miss 
first 100 bytes of the packet contents.

The bug is close to impossible to reproduce without artificial manipulation by 
running threads using debugger.
It might explain why it was not detected so far, since XNET was introduced.

-- 
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-6477) Rare race condition in Plugin Manager could lead to the server crash

[Vlad Khorsun (JIRA)]

Rare race condition in Plugin Manager could lead to the server crash


 Key: CORE-6477
 URL: http://tracker.firebirdsql.org/browse/CORE-6477
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.7
Reporter: Vlad Khorsun
 Attachments: stack.txt



-- 
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-6475) Memory leak when running EXECUTE STATEMENT with named parameters

[Vlad Khorsun (JIRA)]

Memory leak when running EXECUTE STATEMENT with named parameters


 Key: CORE-6475
 URL: http://tracker.firebirdsql.org/browse/CORE-6475
 Project: Firebird Core
  Issue Type: Bug
  Components: API / Client Library
Affects Versions: 4.0 Beta 2
Reporter: Vlad Khorsun


The small memory leak (96 bytes per named parameter) was introduced with 
CORE-5658

-- 
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-6444) Ability to query Firebird configuration using SQL

[Vlad Khorsun (JIRA)]

Ability to query Firebird configuration using SQL
-

 Key: CORE-6444
 URL: http://tracker.firebirdsql.org/browse/CORE-6444
 Project: Firebird Core
  Issue Type: New Feature
  Components: Engine
Reporter: Vlad Khorsun


It will be nice to have ability to query configuration settings using SQL 
language.
Configuration here is contents of firebird.conf, databases.conf and settings 
passed via DPB when applicable.

Proposed solution is to introduce new virtual table to expose settings values. 
Table defined as

CREATE TABLE RDB$CONFIG 
(
RDB$CONFIG_ID   INTEGER NOT NULL,
RDB$CONFIG_NAME VARCHAR(63) CHARACTER SET UTF8 NOT NULL,
RDB$CONFIG_VALUEVARCHAR(255) CHARACTER SET UTF8,
RDB$CONFIG_DEFAULT  VARCHAR(255) CHARACTER SET UTF8,
RDB$CONFIG_IS_SET   BOOLEAN NOT NULL,
RDB$CONFIG_SOURCE   VARCHAR(255) CHARACTER SET UTF8
);

where
- RDB$CONFIG_ID 
  unique row identifier, no special meaning
   
- RDB$CONFIG_NAME  
  setting name, such as "DefaultDbCachePages", "TempCacheLimit" and so on

- RDB$CONFIG_VALUE
  actual value of setting, could be set in configuration and, if necessary, 
"fixed" by the engine (in case of wrong value)

- RDB$CONFIG_DEFAULT
  default value of setting, fixed at Firebird code

- RDB$CONFIG_IS_SET
  TRUE, if value was set by user

- RDB$CONFIG_SOURCE
  name of configuration file where setting was set, relative to the firebird 
root folder, for example: "firebird.conf", "databases.conf"
  or special value "DPB" if setting was set in DPB,
  If setting value was not set, this field contains NULL  

Table RDB$CONFIG is populated from in-memory structures when required and 
instance is kept at SQL query level.
For security reasons access is allowed to the SYSDBA/OWNER only (it could be 
changed before release).
Non-privileged user see empty content, no error is raised (also could be 
changed).


-- 
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-6379) Bugcheck 179

[Vlad Khorsun (JIRA)]

Bugcheck 179 
-

 Key: CORE-6379
 URL: http://tracker.firebirdsql.org/browse/CORE-6379
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 4.0 Beta 2
Reporter: Vlad Khorsun


The bug was detected and reproduced when testing new fb4 feature (statement 
restart on update conflict) but its reason is present in all Firebird versions.

To reproduce start two isql sessions against same database with page size 8KB 

isql 1:
recreate table t5(id int generated by default as identity, x int, s 
varchar(32765) );
insert into t5(x, s) select first 10 0, lpad('', 32765, gen_uuid()) from 
rdb$types;
commit;

update t5 set x = - where id = 3;


isql 2:
set autoddl off;
commit;

set transaction read committed read consistency;
delete from t5;
-- waits for transaction in isql 1

isql 1:
commit;

at this point isql 2 will print:

Statement failed, SQLSTATE = XX000
Error during savepoint backout - transaction invalidated
-internal Firebird consistency check (decompression overran buffer (179), file: 
sqz.cpp line: 293)
Statement failed, SQLSTATE = XX000
internal Firebird consistency check (can't continue after bugcheck)

-- 
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-6364) Wrong reference counting in UDR trigger sample

[Vlad Khorsun (JIRA)]

Wrong reference counting in UDR trigger sample
--

 Key: CORE-6364
 URL: http://tracker.firebirdsql.org/browse/CORE-6364
 Project: Firebird Core
  Issue Type: Bug
  Components: UDF
Affects Versions: 3.0.6, 4.0 Beta 2, 3.0.5, 4.0 Beta 1, 3.0.4, 3.0.3, 4.0 
Alpha 1, 3.0.2, 3.0.1, 3.0.0, 4.0 Initial
Reporter: Vlad Khorsun


Due to not released transaction and attachment interfaces in 
examples\udr\Trigger.cpp there is small memory leak and possible server crash 
on shutdown.


-- 
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] Reopened: (CORE-6253) Crash caused by the locked fb_lock file

[Vlad Khorsun (JIRA)]

 [ 
http://tracker.firebirdsql.org/browse/CORE-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Khorsun reopened CORE-6253:



> Crash caused by the locked fb_lock file
> ---
>
> Key: CORE-6253
> URL: http://tracker.firebirdsql.org/browse/CORE-6253
> Project: Firebird Core
>  Issue Type: Bug
>  Components: Engine
>Affects Versions: 4.0 Beta 1, 3.0.5
> Environment: WI-V3.0.5.33220 Firebird 3.0
> WI-T4.0.0.1779 Firebird 4.0 Beta 1
>Reporter: Basil A. Sidorov
>Assignee: Vlad Khorsun
>Priority: Minor
> Fix For: 3.0.6, 4.0 Beta 2
>
> Attachments: CORE-6253.zip
>
>
> 1. Run Firebird server as application or service, connect in isql to 
> localhost:employee
> 2. Run fb_lock_print -d employee -iw 1 65535
> 3. Disconnect from employee and (normal) shutdown server. fb_lock_ file 
> is not deleted (open in fb_lock_print)
> 3. Run again Firebird server and try again connect to employee. ISQL hung and 
> server fully load one cpu core
> 4. Terminate (Ctrl+C) fb_lock_print and server is crashed.

-- 
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-6351) Computed field could be wrongly evaluated as NULL

[Vlad Khorsun (JIRA)]

Computed field could be wrongly evaluated as NULL
-

 Key: CORE-6351
 URL: http://tracker.firebirdsql.org/browse/CORE-6351
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.6
Reporter: Vlad Khorsun


The sample is based on much more complex case sent to me by user privately.

1. Prepare metatada

create table t1
(
  id int,
  f1 computed by ('abcd'),
  f2 computed by ('xyz')
);
commit;

set term ^;
create or alter procedure p_t1 (id int)
  returns (val varchar(32))
as
begin
  val = 'unknown';

  select f2 from t1 where id = :id
into :val;

  suspend;
end^
set term ;^
commit;

alter table t1
  alter f1 computed by ((select val from p_t1(id)));

alter table t1
  alter f2 computed by ('id = ' || id);
commit;

insert into t1 values (1);
commit;
exit;



2. Test OK

select val from p_t1(1);

VAL

id = 1

select * from t1;

  ID F1   F2
  
   1 id = 1   id = 1

exit;


3. Test FAIL

select * from t1;

  ID F1   F2
  
   1id = 1

select val from p_t1(1);

VAL



exit;


The issue happens when:
- table contains at least two caclulated fields
- first calc field contains expression with PSQL object which used second calc 
field
- the table metadata is loaded into metadata cache before metadata of PSQL 
object mentioned above


-- 
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-6319) NBACKUP locks db file on error

[Vlad Khorsun (JIRA)]

NBACKUP locks db file on error
--

 Key: CORE-6319
 URL: http://tracker.firebirdsql.org/browse/CORE-6319
 Project: Firebird Core
  Issue Type: Bug
  Components: NBACKUP
Affects Versions: 4.0 Beta 2
Reporter: Vlad Khorsun


When I give wrong backup file to NBACKUP.exe -INPLACE, error is reported as 
expected:

NBACKUP -inplace -restore localhost/:Z:\export\TESTF2.FDB Z:\export\x05G.nbk
Invalid incremental backup file: Z:\export\x05G.nbk

NBACKUP -inplace -restore localhost/:Z:\export\TESTF2.FDB Z:\export\x05G.nbk
Invalid incremental backup file: Z:\export\x05G.nbk


But when I do the same using FB Services API (isc_action_svc_nrest, 
isc_spb_options+isc_spb_nbk_inplace, ...)
then after the first error the database will remain locked, and all subsequent 
attempts to work with it raise:
  Statement failed, SQLSTATE = HY000
  Error opening database file: Z:\EXPORT\TESTF2.FDB
  -The process cannot access the file because it is being used by another 
process
The FB server must be restarted to unlock the file.

(tested with Firebird-4.0.0.1963-0-Beta2 and snapshot 
Firebird-4.0.0.1999-0_x64) 

-- 
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-6295) Incomplete header files

[Vlad Khorsun (JIRA)]

Incomplete header files
---

 Key: CORE-6295
 URL: http://tracker.firebirdsql.org/browse/CORE-6295
 Project: Firebird Core
  Issue Type: Bug
  Components: Installation
Affects Versions: 3.0.5, 4.0 Beta 1, 3.0.4, 3.0.3, 4.0 Alpha 1, 3.0.2, 
3.0.1, 3.0.0, 4.0 Initial
Reporter: Vlad Khorsun


\include\firebird\IdlFbInterfaces.h contains references to the PerformanceInfo 
which is declared in \src\jrd\ntrace.h
Contents of this file should be included into final ibase.h

Also, i see no \include\firebird folder in zip kits

-- 
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-6254) AV in engine when using SET TRANSACTION and ON TRANSACTION START trigger uses EXECUTE STATEMENT against current transaction

[Vlad Khorsun (JIRA)]

AV in engine when using SET TRANSACTION and ON TRANSACTION START trigger uses 
EXECUTE STATEMENT against current transaction
---

 Key: CORE-6254
 URL: http://tracker.firebirdsql.org/browse/CORE-6254
 Project: Firebird Core
  Issue Type: Bug
Affects Versions: 3.0.5, 4.0 Beta 1, 3.0.4, 3.0.3, 4.0 Alpha 1, 3.0.2, 
3.0.1, 3.0.0, 4.0 Initial
Reporter: Vlad Khorsun


To reproduce, attach with isql to the any database and run:

set term ^;
create or alter trigger trg_tx_start on transaction start
as
declare tx int;
begin
  execute statement ('select current_transaction from rdb$database')
into :tx;
end
^
set term ;^
commit;

-- new transaction using API, OK
select current_transaction from rdb$database;
commit;

-- new transaction using SQL, AV on commit
set transaction;
select current_transaction from rdb$database;
commit;

drop  trigger trg_tx_start;
commit;



-- 
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-6233) Wrong dependencies of stored function on view after backup and restore

[Vlad Khorsun (JIRA)]

Wrong dependencies of stored function on view after backup and restore
--

 Key: CORE-6233
 URL: http://tracker.firebirdsql.org/browse/CORE-6233
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.5
Reporter: Vlad Khorsun


1. Create database and run script

set term ^;

create or alter view v1 
as
  select 1 as n from rdb$database
^  

create or alter function f1 
  returns integer
as  
declare ret integer;
begin
  select n from v1 into ret;
  return ret;
end
^

create or alter procedure p1
  returns (ret integer)
as  
begin
  select n from v1 into ret;
end
^

set term ;^

2. Check dependencies:

SQL> show function;
Global functions

Function Name Invalid Dependency, Type
= === =
F1V1, View

SQL> show procedure;
Global procedures

Procedure NameInvalid Dependency, Type
= === =
P1V1, View

Result: dependencies is OK

3. backup database and restore backup into new database (using gbak)

4. connect to the restored database and check dependencies

SQL> show function;
Global functions

Function Name Invalid Dependency, Type
= === =
F1RDB$PAGES, Table

SQL> show procedure;
Global procedures

Procedure NameInvalid Dependency, Type
= === =
P1V1, View

Result: dependencies of function F1 is wrong, while dependencies of procedure 
P1 is OK


-- 
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-6150) Bugcheck when PK\UK\FK constraint check read record already marked as damaged

[Vlad Khorsun (JIRA)]

Bugcheck when PK\UK\FK constraint check read record already marked as damaged 
--

 Key: CORE-6150
 URL: http://tracker.firebirdsql.org/browse/CORE-6150
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 2.5.9, 4.0 Beta 1, 3.0.4, 3.0.3, 2.5.8, 4.0 Alpha 1, 
3.0.2, 2.5.7, 3.0.1, 2.5.6, 3.0.0, 4.0 Initial, 2.5.5, 2.5.4, 2.5.3 Update 1, 
2.1.7, 2.5.3, 2.5.2 Update 1, 2.5.2, 2.5.1, 2.5.0
Reporter: Vlad Khorsun


I have customer (private) database with few records marked as damaged (by gfix 
-mend).
When new record inserted refers to the damaged record, engine tries to read 
damaged record and fails with a bugcheck error.
Correct behaviout is to skip damaged record as it is already done by usual 
SELECT statement processing.


-- 
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-6142) Error "connection lost to database" could happen when application creates few local attachments (using XNET) simultaneously

[Vlad Khorsun (JIRA)]

Error "connection lost to database" could happen when application creates few 
local attachments (using XNET) simultaneously
---

 Key: CORE-6142
 URL: http://tracker.firebirdsql.org/browse/CORE-6142
 Project: Firebird Core
  Issue Type: Bug
  Components: API / Client Library
Affects Versions: 2.5.9, 4.0 Beta 1, 3.0.4, 3.0.3, 2.5.8, 4.0 Alpha 1, 
3.0.2, 2.5.7, 3.0.1, 2.5.6, 3.0.0, 4.0 Initial, 2.5.5, 2.5.4, 2.5.3 Update 1, 
2.1.7, 2.5.3, 2.5.2 Update 1, 2.5.2, 2.5.1, 2.5.0
 Environment: Windows only, mt-application, local protocol
Reporter: Vlad Khorsun




-- 
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] Reopened: (CORE-6080) Attempt to drop existing user randomly fails with "336723990 : record not found for user"

[Vlad Khorsun (JIRA)]

 [ 
http://tracker.firebirdsql.org/browse/CORE-6080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Khorsun reopened CORE-6080:



Re-opened to fix a bug, introduced by initial attempt

> Attempt to drop existing user randomly fails with "336723990 : record not 
> found for user"
> -
>
> Key: CORE-6080
> URL: http://tracker.firebirdsql.org/browse/CORE-6080
> Project: Firebird Core
>  Issue Type: Bug
>  Components: Engine
>Affects Versions: 4.0 Beta 1
> Environment: v4 Classic Server only
>Reporter: Pavel Zotov
>Assignee: Vlad Khorsun
> Fix For: 4.0 Beta 2
>
>
> This ticket was created by Vlad request after discuss failures in test for 
> CORE-6038 when it is launched
> Consider following batch:
> =
> @echo off
> setlocal enabledelayedexpansion enableextensions
> for /f "delims=." %%a in ('wmic os get localdatetime ^| findstr /i /r /b 
> /c:"[0-9]"') do (
>   set dts=%%a
>   set ymd=!dts:~2,6!
>   set hms=!dts:~8,6!
> )
> set fbc=C:\FB\40CS
> set dbpath=c:\temp
> set authplg=Srp
> @rem set authplg=Legacy_UserManager
> set dbnm=!dbpath!\c6038.fdb.tmp
> set sql=!dbpath!\%~n0.sql.tmp
> set tmp=!dbpath!\%~n0.tmp.tmp
> set err=!dbpath!\%~n0.err.tmp
> set log=%~dpn0.!ymd!_!hms!.log
> if exist !dbnm! del !dbnm!
> (
> echo set bail on;
> echo create database 'localhost:!dbnm!' user sysdba password 'masterkey';
> echo commit;
> echo alter database set linger to 30;
> echo commit;
> echo show database;
> ) >!tmp!
> !fbc!\isql.exe -z -q -i !tmp!
> !fbc!\gfix.exe -w async localhost:!dbnm! -user sysdba -password masterkey
> (
> echo connect 'localhost:!dbnm!' user sysdba password 'masterkey';
> echo create or alter user c6038_srp password 'c6038_srp' using plugin 
> !authplg!;
> echo commit;
> echo connect 'localhost:!dbnm!' user c6038_srp password 'c6038_srp';
> echo commit;
> echo connect 'localhost:!dbnm!' user sysdba password 'masterkey';
> echo drop user c6038_srp using plugin !authplg!; 
> ) > !sql!
> !fbc!\fbsvcmgr.exe localhost:service_mgr user sysdba password masterkey 
> info_server_version >!tmp!
> type !tmp!
> type !tmp! >>!log!
> echo !date! !time! Started.
> if exist !err! del !err!
> set verb=1
> set /a n=300
> set /a i=0
> :m1
> set /a i=!i!+1
> if !verb! EQU 1 (
> echo !date! !time!, attempt !i! >!tmp!
> type !tmp!
> type !tmp! >>!log!
> del !tmp!
> for /f "usebackq tokens=*" %%a in ('!err!') do set size=%%~za
> if !size! gtr 0 (
> echo CONNECTION FAILED IN ITERATION # !i!. CHECK ERROR LOG:
> type !err!
> type !err! >>!log!
> exit
> )
> )
> !fbc!\isql.exe -q -i !sql! 1>>!err! 2>&1
> if !i! GEQ !n! (
> echo !date! !time! Completed.
> for /f "usebackq tokens=*" %%a in ('!err!') do set size=%%~za
> if !size! gtr 0 (
> echo CHECK ERROR LOG AFTER ALL ITERATIONS:
> type !err!
> type !err! >>!log!
> )
> exit
> )
> goto m1
> =
> Change in it only these three settings: fbc, dbpath and authplg.
> Prepare FB to work as Classic and run this batch.
> On WI-T4.0.0.1524 you will soon encounter with:
> =
> 10.06.2019 18:13:19.67, attempt 1 
> 10.06.2019 18:13:20.72, attempt 2 
> . . .
> 10.06.2019 18:13:49.75, attempt 27 
> 10.06.2019 18:13:50.79, attempt 28 
> Statement failed, SQLSTATE = HY000
> modify record error
> After line 1 in file c:\temp\c6038.leg.sql.tmp
> Statement failed, SQLSTATE = 28000
> Your user name and password are not defined. Ask your database administrator 
> to set up a Firebird login.
> After line 3 in file c:\temp\c6038.leg.sql.tmp
> Statement failed, SQLSTATE = HY000
> record not found for user: C6038_SRP
> =
> Trace with 'log_prepare_statements = true' will show:
> 1) TWO prepare_statement events before point when error raises:
> PREPARE_STATEMENT 
> drop user c6038_srp using plugin Srp
> 
> PREPARE_STATEMENT 
> drop user c6038_srp using plugin Srp
> 2) SUCCESSFUL finish of executed statement:
> EXECUTE_STATEMENT_FINISH
> drop user c6038_srp using plugin Srp
> 0 records fetched
>   0 ms
> and immediately after this - error:
> 3) ERROR AT JTransaction::commit
> C:\TEMP\C6038.FDB.TMP (ATT_55, SYSDBA:NONE, NONE, TCPv6:::1/63982)
> C:\FB\40SS\isql.exe:5124
> 336723990 : record not found for user: C6038_SRP

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

[Firebird-devel] [FB-Tracker] Created: (CORE-5993) When creation of audit log file fails, there is no error message in firebird.log

[Vlad Khorsun (JIRA)]

When creation of audit log file fails, there is no error message in firebird.log


 Key: CORE-5993
 URL: http://tracker.firebirdsql.org/browse/CORE-5993
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.4, 3.0.3, 4.0 Alpha 1, 3.0.2, 3.0.1, 3.0.0, 4.0 
Initial
Reporter: Vlad Khorsun




-- 
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-5991) Trace could not work correctly with quoted file names in trace configurations

[Vlad Khorsun (JIRA)]

Trace could not work correctly with quoted file names in trace configurations
-

 Key: CORE-5991
 URL: http://tracker.firebirdsql.org/browse/CORE-5991
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.4, 3.0.3, 4.0 Alpha 1, 3.0.2, 3.0.1, 3.0.0, 4.0 
Initial
Reporter: Vlad Khorsun
Priority: Minor


Trace configuration allows to specify file names in two places:
a) at "database" section header as file name pattern
b) at "log_filename" parameter, used to specify file name for audit log

Double quotes works as expected, the issue is about single quoted values.


When trace session with such configuration is active and user attached to some 
database, 
the following happens:

In the case (a) error is reported:

Error creating trace session for database "DBNAME":
error while parsing trace configuration
line 15: error while compiling regular expression "'PATTERN'"

where DBNAME is the database name from connection string and 'PATTERN' is 
database pattern from trace configuration.
Error is reported via trace log (in case of user trace session) or firebird.log 
(in case of audit trace session).


In the case (b) the audit log file is not created and error is not logged (it 
will be adressed in separate ticket).


-- 
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-5990) Pool of external connections

[Vlad Khorsun (JIRA)]

Pool of external connections


 Key: CORE-5990
 URL: http://tracker.firebirdsql.org/browse/CORE-5990
 Project: Firebird Core
  Issue Type: New Feature
  Components: Engine
Reporter: Vlad Khorsun


To avoid delays when external connections established frequently, external 
data source (EDS) subsystem is supplemented by the pool of external connections.
The pool keeps unused external connections for some time and allows to avoid 
the 
cost of connecting / disconnecting for frequently used connection strings.


-- 
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-5954) Garbage collection in intermediate record versions

[Vlad Khorsun (JIRA)]

Garbage collection in intermediate record versions
--

 Key: CORE-5954
 URL: http://tracker.firebirdsql.org/browse/CORE-5954
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Reporter: Vlad Khorsun


The ticket is created for documentation purposes.

The more detailed description is at
doc\README.read_consistency.md

-- 
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-5953) Statement level read consistency in read-committed transactions

[Vlad Khorsun (JIRA)]

Statement level read consistency in read-committed transactions
---

 Key: CORE-5953
 URL: http://tracker.firebirdsql.org/browse/CORE-5953
 Project: Firebird Core
  Issue Type: New Feature
  Components: Engine
Reporter: Vlad Khorsun


The ticket is created for documentation purposes.

The more detailed description is at 
doc\README.read_consistency.md

-- 
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-5935) Bugcheck 165 (cannot find tip page)

[Vlad Khorsun (JIRA)]

Bugcheck 165 (cannot find tip page) 


 Key: CORE-5935
 URL: http://tracker.firebirdsql.org/browse/CORE-5935
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.4, 3.0.3, 3.0.2, 3.0.1, 3.0.0
 Environment: Classic, SuperClassic
Reporter: Vlad Khorsun




-- 
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-5921) Provide information about Global Commit Number, Commit Number of currently used database snapshot (if any) and Commit Numbers assigned to the committ

[Vlad Khorsun (JIRA)]

Provide information about Global Commit Number, Commit Number of currently used 
database snapshot (if any) and Commit Numbers assigned to the committed 
transactions


 Key: CORE-5921
 URL: http://tracker.firebirdsql.org/browse/CORE-5921
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Affects Versions: 4.0 Alpha 1
Reporter: Vlad Khorsun




-- 
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-5913) Add context variables with compression and encryption status of current connection

[Vlad Khorsun (JIRA)]

Add context variables with compression and encryption status of current 
connection
--

 Key: CORE-5913
 URL: http://tracker.firebirdsql.org/browse/CORE-5913
 Project: Firebird Core
  Issue Type: Sub-task
Reporter: Vlad Khorsun
Assignee: Vlad Khorsun




-- 
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-5911) Connection could hung after no activity for 60 seconds

[Vlad Khorsun (JIRA)]

Connection could hung after no activity for 60 seconds
--

 Key: CORE-5911
 URL: http://tracker.firebirdsql.org/browse/CORE-5911
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.3, 2.5.8, 4.0 Alpha 1
 Environment: INET connections only
Reporter: Vlad Khorsun


Imagine application that run some query then sleep for 60 seconds then again 
run query, sleep for 60 sec and so on.

If there are no other connections, or if this is ClassicServer - there could 
happen a race condition when last (only) worker 
thread in network listener exits due to idle timeout (60 sec) and new request 
is arrived at the same time and left not 
processed in queue. 
In the case of SS\SC any new request from the other connection will "awake" 
network server and that request will be 
processed, but in the case of CS this is impossible and connection will hung.

The bug is at the thread pool of network listener and can't happen for XNET and 
WNET protocols which not uses thread pool.

-- 
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-5872) Database validation reports false errors "Record XXX has bad transaction" and\or "Record XXX is wrong length" when record transaction number is great

[Vlad Khorsun (JIRA)]

Database validation reports false errors "Record XXX has bad transaction" 
and\or "Record XXX is wrong length" when record transaction number is greater 
than 2^32
-

 Key: CORE-5872
 URL: http://tracker.firebirdsql.org/browse/CORE-5872
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.3, 4.0 Alpha 1, 3.0.2, 3.0.1, 3.0.0, 4.0 Initial
Reporter: Vlad Khorsun




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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5870) ISQL's show_database command works wrong with big numbers

[Vlad Khorsun (JIRA)]

ISQL's show_database command works wrong with big numbers
-

 Key: CORE-5870
 URL: http://tracker.firebirdsql.org/browse/CORE-5870
 Project: Firebird Core
  Issue Type: Bug
  Components: ISQL
Affects Versions: 3.0.3, 4.0 Alpha 1, 3.0.2, 3.0.1, 3.0.0, 4.0 Initial
Reporter: Vlad Khorsun
Priority: Minor


\firebird>gstat -h s:\temp\tx.30.fdb

Database "S:\TEMP\TX.30.FDB"
Gstat execution time Tue Jul 10 18:32:41 2018

Database header page information:
Flags   0
Generation  1977120
System Change Number0
Page size   16384
ODS version 12.0
Oldest transaction  4294965022
Oldest active   4294985534
Oldest snapshot 4294985534
Next transaction4294985534
...

while isql show zero's:

\firebird>isql s:\temp\tx.30.fdb
Database: s:\temp\tx.30.fdb, User: SYSDBA
SQL> show database;
Database: s:\temp\tx.30.fdb
Owner: SYSDBA
PAGE_SIZE 16384
Number of DB pages allocated = 68818
Number of DB pages used = 66037
Number of DB pages free = 2781
Sweep interval = 0
Forced Writes are OFF
Transaction - oldest = 0
Transaction - oldest active = 0
Transaction - oldest snapshot = 0
Transaction - Next = 0
ODS = 12.0
Database not encrypted
Default Character set: NONE

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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5869) Sweep can't move OIT value over 2^32, when Next already greater than 2^32 (4'294'967'296)

[Vlad Khorsun (JIRA)]

Sweep can't move OIT value over 2^32, when Next already greater than 2^32 
(4'294'967'296)
-

 Key: CORE-5869
 URL: http://tracker.firebirdsql.org/browse/CORE-5869
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.3, 3.0.2, 3.0.1, 3.0.0
Reporter: Vlad Khorsun


First sweep run:

Sweep is started by SYSDBA
Database "S:\TEMP\TX.30.FDB" 
OIT 4294965022, OAT 4294985533, OST 4294985533, Next 4294985533


Sweep is finished
Database "S:\TEMP\TX.30.FDB" 
OIT 18238, OAT 4294985533, OST 4294985533, Next 4294985534

Run sweep again 

Sweep is started by SYSDBA
Database "S:\TEMP\TX.30.FDB" 
OIT 4294965022, OAT 4294985534, OST 4294985534, Next 4294985534


Sweep is finished
Database "S:\TEMP\TX.30.FDB" 
OIT 18239, OAT 4294985534, OST 4294985534, Next 4294985535

Note: 
- OIT is less than 2^32 (4'294'965'022 < 4'294'967'296), while Next is greater 
than 2^32 (4'294'985'534 > 4'294'967'296)
- OIT is the same at both "Sweep is started" message , i.e. it was not moved by 
sweep
- "Sweep is finished" message contains wrong OIT value (truncated to 32-bit 
number)


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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5847) "Malformed string" instead of key value in PK violation error message

[Vlad Khorsun (JIRA)]

"Malformed string" instead of key value in PK violation error message
-

 Key: CORE-5847
 URL: http://tracker.firebirdsql.org/browse/CORE-5847
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.3, 2.5.8, 4.0 Alpha 1, 3.0.2, 2.5.7, 3.0.1, 2.5.6, 
3.0.0, 4.0 Initial, 2.5.5, 2.5.4, 2.5.3 Update 1, 2.5.3
Reporter: Vlad Khorsun
Priority: Minor


1. Connect with UTF8 charset:

firebird>isql -ch utf8

SQL> recreate table t (uid char(16) character set octets primary key);
SQL> commit;
SQL>
SQL>
SQL> insert into t values (GEN_UUID());
SQL> select * from t;

UID

E5FCB3D11EB7472792F4819B06CB7099

SQL> insert into t select uid from t;
Statement failed, SQLSTATE = 23000
violation of PRIMARY or UNIQUE KEY constraint "INTEG_2" on table "T"
-Malformed string



2. Connect with non-UTF8 charset:

firebird>isql -ch win1251 

SQL> insert into t select uid from t;
Statement failed, SQLSTATE = 23000
violation of PRIMARY or UNIQUE KEY constraint "INTEG_2" on table "T"
-Problematic key value is ("UID" = x'E5FCB3D11EB7472792F4819B06CB7099')


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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Reopened: (CORE-5436) [FB3 SC] Server hangs (under load test)

[Vlad Khorsun (JIRA)]

 [ 
http://tracker.firebirdsql.org/browse/CORE-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Khorsun reopened CORE-5436:



New reports from users allows to find another reason for this issue.
Thus i re-open the ticket


> [FB3 SC] Server hangs (under load test)
> ---
>
> Key: CORE-5436
> URL: http://tracker.firebirdsql.org/browse/CORE-5436
> Project: Firebird Core
>  Issue Type: Bug
>  Components: Engine
>Affects Versions: 3.0.2
> Environment: Firebird 3.0.2.32651 SuperClassic x64, Win10, IBProvider 
> Test System.
>Reporter: Kovalenko Dmitry
>Assignee: Vlad Khorsun
> Fix For: 4.0 Beta 1, 3.0.4
>
>
> SuperClassic hangs under load test.
> ---
> Two test processes (with 4 test theads) with own (two) databases.
> All test threads are waiting the answer from "database attach" operation.
> - [Error at client side]
> [THR:001544] [05.01.2017 11:44:09] [test] Verify Arrays 
> [TBL_CS__NONE::CHAR_ARRAY__8]. ArrayRwMode: direct. BindArrayType: 
> array_iunknown__ibp_ss_wc. CType:UNICODE_FSS Truncate Char: false
> [THR:001544] [05.01.2017 11:44:29] ERROR: 
> [array.002.rw_api.build_mode__use_cmd.unicode.TBL_CS__NONE.CHAR_ARRAY__8.chars__WIN1251.write__array_iunknown__ibp_ss_wc.ctype__UTF8]
>  Data Source initialization
> 1. [Unknown DBMS]: Error occurred during login, please check server 
> firebird.log for details
> 2. [LCPI.IBProvider.3]: Ошибка подключения к базе данных.
> Неопознанная ошибка
> COM Error Code: E_FAIL
> - [Error in firebird.log]
> HOME4 Thu Jan  5 11:44:19 2017
>   Database: D:\PROGRAM_FILES\FIREBIRD_3_0_X64\SECURITY3.FDB
>   page 0, page type 1 lock denied (216)
> HOME4 Thu Jan  5 11:44:29 2017
>   Database: 
>   page 0, page type 1 lock denied (216)
> HOME4 Thu Jan  5 11:44:29 2017
>   Authentication error
>   page 0, page type 1 lock denied
> --
> Dump file, Sources, PDB, EXE, DLL - http://dropmefiles.com/qlTUB

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

   

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5843) Wrong handling of failures of TRANSACTION START trigger

[Vlad Khorsun (JIRA)]

Wrong handling of failures of TRANSACTION START trigger
---

 Key: CORE-5843
 URL: http://tracker.firebirdsql.org/browse/CORE-5843
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 4.0 Alpha 1
Reporter: Vlad Khorsun


There are two general cases when TRANSACTION START trigger is fired
1. when user start transaction, and
2. when IN AUTONOMOUS TRANSACTION statement starts new transaction.

Let look what happens if TRANSACTION START is present and raises error.

According to documentation (see README.db_triggers.txt):

- TRANSACTION START
Triggers are fired in the newly user created transaction - uncaught
exceptions are returned to the client and the transaction is rolled-back.

In the 1st case new transaction is not rolled-back currently and left active 
until Firebird process alive.
In the 2nd case new transaction is rolled-back but it also fires TRANSACTION 
ROLLBACK trigger
which is wrong. Note, in the 1st case TRANSACTION ROLLBACK trigger is not fired.

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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5837) Inconsistent results when working with GLOBAL TEMPORARY TABLE ON COMMIT PRESERVE ROWS

[Vlad Khorsun (JIRA)]

Inconsistent results when working with GLOBAL TEMPORARY TABLE ON COMMIT 
PRESERVE ROWS
-

 Key: CORE-5837
 URL: http://tracker.firebirdsql.org/browse/CORE-5837
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.3, 4.0 Alpha 1, 3.0.2, 3.0.1, 3.0.0, 4.0 Initial
 Environment: SuperServer only
Reporter: Vlad Khorsun


One attachment could see data of GTT instance of another attachment.
Bugcheck 185 or 186 could happens on rollback if transaction works with some 
GTT.

GTT here is GLOBAL TEMPORARY TABLE ON COMMIT PRESERVE ROWS.
GLOBAL TEMPORARY TABLE ON COMMIT DELETE ROWS is not affected.

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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5832) Implement way to reset user session environment to its initial (default) state

[Vlad Khorsun (JIRA)]

Implement way to reset user session environment to its initial (default) state
--

 Key: CORE-5832
 URL: http://tracker.firebirdsql.org/browse/CORE-5832
 Project: Firebird Core
  Issue Type: New Feature
  Components: Engine
Reporter: Vlad Khorsun


Resetting user session (connection) to its initial state should be useful when 
session is reused by application.
I.e. instead of detach\attach application could just reuse already established 
connection.
To reuse connection all its user context variables, contents of temporary 
tables etc should be cleared and all 
session-level settings should be reset to its default values.

The proposed solution is to implement new session management SQL statement

ALTER SESSION RESET

It will 
- reset DECFLOAT parameters (BIND, TRAP and ROUND) to its default values
- reset session and statement timeouts to zero
- remove all context variables in 'USER_SESSION' namespace 
- clear contents of all used GLOBAL TEMPORARY TABLE ... ON COMMIT PRESERVE ROWS
- restore ROLE which was passed with DPB and clear all cached security classes 
(if role was changed)

Note, CURRENT_USER will not be changed.

See also discussion at fb-devel, thread "RFC: External Connections Pool" 
started at 18.05.2018

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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5831) Not user friendly output of gstat at encrypted database

[Vlad Khorsun (JIRA)]

Not user friendly output of gstat at encrypted database
---

 Key: CORE-5831
 URL: http://tracker.firebirdsql.org/browse/CORE-5831
 Project: Firebird Core
  Issue Type: Bug
  Components: GSTAT
Affects Versions: 3.0.3
Reporter: Vlad Khorsun
Priority: Minor


Gstat shows "strange" lines "Variable header data" section at on encrypted 
database:

> gstat -h ...

Database header page information:
..
Implementation  HW=Intel/i386 little-endian OS=Windows CC=MSVC
Shadow count0
Page buffers2048
Next header page0
Clumplet End216
Database dialect3
Creation date   Sep 7, 2017 15:41:14
Attributes  force write, encrypted, crypt process, plugin 
cryptDB

Variable header data:
Encoded option 5, length 28
Key hash:   Y57pr6T1PsnNkgLpaIVupsmvhmM=
Unrecognized option 11, length 16
Sweep interval: 0
*END*

Look at 1st and 3rd liens after "Variable header data"

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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5819) Attachment could not gone after it was DELETE'd FROM MON$ATTACHMENTS

[Vlad Khorsun (JIRA)]

Attachment could not gone after it was DELETE'd FROM MON$ATTACHMENTS


 Key: CORE-5819
 URL: http://tracker.firebirdsql.org/browse/CORE-5819
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.3, 4.0 Alpha 1, 3.0.2, 3.0.1, 3.0.0, 4.0 Initial
 Environment: Attachment run some EXECUTE STATEMENT when it was 
asynchronously dropped (using DELETE FROM MON$ATTACHMENTS).

Reporter: Vlad Khorsun


It was reproduced using OLTP-EMUL test with 10 active connections. 
Separate isql session issue DELETE FROM MON$ATTACHMENTS statement and not all 
attachments was finally detached, one was freeze at detach stage.

Stack traces

1. First thread run regular detach, hold blockingMutex and wait for zero at 
att_purge_tid :

engine12.dll!purge_attachment(0x10bc14a0, 0x154ef958, 
3) Line 6904  C++
engine12.dll!Jrd::JAttachment::freeEngineData(0x07fee784ca32, 88) 
Line 2935 C++

engine12.dll!Firebird::IAttachmentBaseImpl > > >::cloopdetachDispatcher(0x0863adc8, 0x154ef958) Line 
8898   C++
fbclient.dll!Why::YAttachment::detach(0x154ef958) Line 5460 
C++

fbclient.dll!Firebird::IAttachmentBaseImpl > > >::cloopdetachDispatcher(0x0e1c3640, 0x0de76cc0) Line 
8898   C++
firebird.exe!rem_port::disconnect(0x0de76cc0, 
0x0de76cc0) Line 2866 C++
firebird.exe!process_packet(0x0dd8f5c0, 0x0dd8f5c0, 
0x, 0x0001) Line 4568   C++
firebird.exe!loopThread(0x007a) Line 5973   C++
firebird.exe!threadStart(0x) Line 93C++


2. Second thread run asyncronous detach, set set att_purge_tid, cleanup 
assotiated EDS::InternalConnection and wait for blockingMutex:

ntdll.dll!NtWaitForSingleObject()   Unknown
ntdll.dll!RtlpWaitOnCriticalSection()   Unknown
ntdll.dll!RtlEnterCriticalSection() Unknown
engine12.dll!`anonymous 
namespace'::AttachmentHolder::AttachmentHolder(0x07fee5503288, 
0x0c96f100, 0, 0x07fee5503288) Line 675  C++
engine12.dll!`anonymous 
namespace'::EngineContextHolder::EngineContextHolder(0x1564ecc0,
 0x, 0x0002c78e, 0) Line 753   C++
engine12.dll!Jrd::JStatement::freeEngineData(0x0b498b08) Line 
4943  C++
engine12.dll!EDS::InternalStatement::doClose(0x, 208) 
Line 604  C++
engine12.dll!EDS::Statement::deallocate(0x0c96fcf0) Line 1026   
C++
engine12.dll!EDS::Statement::deleteStatement(0x15643f98, 
0x) Line 845   C++
engine12.dll!EDS::Connection::clearStatements(0x15648398) Line 
492  C++
engine12.dll!EDS::Connection::detach(0x15648398) Line 510   
C++
engine12.dll!EDS::Connection::deleteConnection(0x15648398, 
0x0001) Line 310 C++
engine12.dll!EDS::Provider::releaseConnection(0x, 
{...}, 240) Line 250  C++
engine12.dll!EDS::Connection::deleteTransaction(0x0c96fcf0, 
0x) Line 401C++
engine12.dll!EDS::Transaction::rollback(0x07fefc6811ac, 88) Line 
707C++
engine12.dll!EDS::Transaction::jrdTransactionEnd(0x0c96fcf0, 
0x15642768, false, false, false) Line 788  C++
engine12.dll!TRA_rollback(0x0c96fcf0, 0x21d43ff0, 
false, 208) Line 1319 C++
engine12.dll!purge_transactions(0x1039b140, 0x0b498ae0, 
false) Line 6850C++
engine12.dll!purge_attachment(0x11c23b40, 0x11c23b40, 
1) Line 7024  C++
engine12.dll!`anonymous 
namespace'::shutdownAttachments(0x11c23b40, 224) Line 7379  C++
engine12.dll!`anonymous 
namespace'::attachmentShutdownThread(0x11c23b40) Line 7408  C++
engine12.dll!threadStart(0x) Line 93C++


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



--
Check 

[Firebird-devel] [FB-Tracker] Created: (CORE-5781) Implement INSENSITIVE property for PSQL explicit cursors

[Vlad Khorsun (JIRA)]

Implement INSENSITIVE property for PSQL explicit cursors


 Key: CORE-5781
 URL: http://tracker.firebirdsql.org/browse/CORE-5781
 Project: Firebird Core
  Issue Type: New Feature
  Components: Engine
Reporter: Vlad Khorsun


The SQL Standard say:

--- begin quote ---

The following paragraphs define several terms used to discuss issues relating 
to a cursor's operational sensitivity
property:

A change to SQL-data is said to be independent of a cursor CR if and only if it 
is not made by an  or a  that is positioned 
on CR.

A change to SQL-data is said to be significant to CR if and only if it is 
independent of CR, and, had it been
committed before CR was opened, would have caused the sequence of rows in the 
result set descriptor of CR
to be different in any respect.

A change to SQL-data is said to be visible to CR if and only if it has an 
effect on the sequence of rows SR of
the result set descriptor of CR by inserting a row in SR, deleting a row from 
SR, changing the value of a column
of a row of SR, or reordering the rows of SR.

If a cursor is open, and the SQL-transaction in which the cursor was opened 
makes a significant change to
SQL-data, then whether that change is visible through that cursor before it is 
closed is determined as follows:
— If the cursor is insensitive, then significant changes are not visible.
— If the cursor is sensitive, then significant changes are visible.
— If the cursor is asensitive, then the visibility of significant changes is 
implementation-dependent.

--- end quote ---

This ticket offers to implement INSENSITIVE PSQL explicit cursors.
Current implementation is ASENSITIVE - ability of cursor to see significant 
changes is dependent on execution plan.
Implementation of SENSITIVE cursors is out of scope of this ticket.


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

   

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Reopened: (CORE-405) Garbage vs indices/constraints

[Vlad Khorsun (JIRA)]

 [ 
http://tracker.firebirdsql.org/browse/CORE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Khorsun reopened CORE-405:
---

  Assignee: Vlad Khorsun

> Garbage vs indices/constraints
> --
>
> Key: CORE-405
> URL: http://tracker.firebirdsql.org/browse/CORE-405
> Project: Firebird Core
>  Issue Type: Bug
>  Components: Engine
>Reporter: Dmitry Yemanov
>Assignee: Vlad Khorsun
>
> SFID: 744175#
> Submitted By: dimitr
> If an index contains garbage and automatic GC 
> is disabled, then it's impossible to create unique 
> indices or PK/UK/FK constraints.
> For example:
> 1) attach with isc_dpb_no_garbage_collect
> 2) insert some duplicate data
>   INSERT INTO T1 (F1) VALUES (1);
>   INSERT INTO T1 (F1) VALUES (1);
> 3) delete these rows
>   DELETE FROM T1;
> 4) create unique index
>   CREATE UNIQUE INDEX IDX1 ON T1 (F1);
> You'll see "attempt to store duplicate value ..." 
> error message, which is incorrect in this case.
> Since indices work outside transaction control, it 
> may be a initial design/implementation pitfall. It 
> appears the index creation and partner lookup 
> code never touches records and hence is unable 
> to determine which versions are actual at the 
> moment of index creation.

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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5727) Make faster engine response on cancel\shutdown signals when scanning long list of pointer pages

[Vlad Khorsun (JIRA)]

Make faster engine response on cancel\shutdown signals when scanning long list 
of pointer pages
---

 Key: CORE-5727
 URL: http://tracker.firebirdsql.org/browse/CORE-5727
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Affects Versions: 2.5.8, 4.0 Alpha 1, 3.0.2
Reporter: Vlad Khorsun




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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5720) Sweep in Firebird 3 in CS mode could run too slow when there is big load on server

[Vlad Khorsun (JIRA)]

Sweep in Firebird 3 in CS mode could run too slow when there is big load on 
server
--

 Key: CORE-5720
 URL: http://tracker.firebirdsql.org/browse/CORE-5720
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 4.0 Alpha 1, 3.0.2, 3.0.1, 3.0.0, 4.0 Initial
Reporter: Vlad Khorsun




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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5719) FB3 crashes when restoring backup made by FB2.5

[Vlad Khorsun (JIRA)]

FB3 crashes when restoring backup made by FB2.5
---

 Key: CORE-5719
 URL: http://tracker.firebirdsql.org/browse/CORE-5719
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.2
Reporter: Vlad Khorsun




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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5704) Avoid UPDATE of RDB$DATABASE by ALTER DATABASE statement when possible

[Vlad Khorsun (JIRA)]

Avoid UPDATE of RDB$DATABASE by ALTER DATABASE statement when possible
--

 Key: CORE-5704
 URL: http://tracker.firebirdsql.org/browse/CORE-5704
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Reporter: Vlad Khorsun


Some clauses of ALTER DATABASE statement requires to update row in RDB$DATABASE:
  SET DEFAULT CHARACTER SET, SET LINGER, DROP LINGER.

Other clauses doesn't requires to update RDB$DATABASE: 
  BEGIN|END BACKUP, ENCRYPT, DECRYPT, etc

Internally, engine runs such UPDATE despite the kind of clause specified by the 
user. 
It is necessary to prevent concurrent run of ALTER DATABASE statements by 
parallel transactions.

Unfortunately, such dummy update blocks other transactions which reads 
RDB$DATABASE in READ COMMITTED NO RECORD VERSION mode.
Usually such blockage is very short, but in case of ALTER DATABASE END BACKUP 
it could be up to tens of minutes.

For example: user complains that isql can not connect with isql to the database 
while ALTER DATABASE END BACKUP is running.
Actually, isql connects successfully, but it reads RDB$DATABASE itself right 
after attachment (using READ COMMITTED NO RECORD 
VERSION WAIT transaction) and waits until ALTER DATABASE END BACKUP commits. 

The improvement is to avoid dummy update of RDB$DATABASE when possible and use 
implicit lock to prevent concurrent run
of ALTER DATABASE statement.

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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5703) When database validation fixes "orphan page" errors it also should adjust "lowest free page" marker (pip_min) on corresponding PIP, if necessary

[Vlad Khorsun (JIRA)]

When database validation fixes "orphan page" errors it also should adjust 
"lowest free page" marker (pip_min) on corresponding PIP, if necessary


 Key: CORE-5703
 URL: http://tracker.firebirdsql.org/browse/CORE-5703
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Reporter: Vlad Khorsun




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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5685) Sometime it is impossible to cancel\kill connection executing external query

[Vlad Khorsun (JIRA)]

Sometime it is impossible to cancel\kill connection executing external query


 Key: CORE-5685
 URL: http://tracker.firebirdsql.org/browse/CORE-5685
 Project: Firebird Core
  Issue Type: Bug
  Components: API / Client Library
Affects Versions: 4.0 Alpha 1, 3.0.2, 2.5.7, 3.0.1, 2.5.6, 3.0.0, 4.0 
Initial, 2.5.5, 2.5.4, 2.5.3 Update 1, 2.5.3, 2.5.2 Update 1, 2.5.2, 2.5.1, 
2.5.0
Reporter: Vlad Khorsun


There is user reports that in some cases they can't kill connections. Memory 
dumps shows that such connection executed external query 
and waits for responce from remote side. There is a suspicion that network 
between local and remote servers could be a reason.
Currently, when local connection is about to be killed, it send cancellation 
request to the remote side (if external query it executed, of course). 
It seems that it could be not enough in some cases.


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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5681) AV when external statement is executed and local transaction is rolled back

[Vlad Khorsun (JIRA)]

AV when external statement is executed and local transaction is rolled back
---

 Key: CORE-5681
 URL: http://tracker.firebirdsql.org/browse/CORE-5681
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 4.0 Alpha 1, 3.0.2, 2.5.7, 3.0.1, 2.5.6, 3.0.0, 4.0 
Initial, 2.5.5, 2.5.4, 2.5.3 Update 1, 2.5.3, 2.5.2 Update 1, 2.5.2, 2.5.1, 
2.5.0
Reporter: Vlad Khorsun


Crash of Firebird 2.5 on Linux was reported by user, below is call stack

#1  0x7fb4bf20dc64 in EDS::Statement::close (this=0x7fb4a37c38f0, 
tdbb=0x7fb4bd608680) at ../src/jrd/extds/ExtDS.cpp:1570
#2  0x7fb4bf1171e8 in EXE_unwind (tdbb=0x7fb4bd608680, 
request=0x7fb4afa69010) at ../src/jrd/exe.cpp:1103
#3  0x7fb4bf1a5879 in close_procedure (tdbb=0x7fb4bc1ff188, rsb=) at ../src/jrd/rse.cpp:625
#4  0x7fb4bf117180 in EXE_unwind (tdbb=0x7fb4bd608680, 
request=0x7fb4a8359040) at ../src/jrd/exe.cpp:1092
#5  0x7fb4bf14db1b in JRD_unwind_request (tdbb=0x7fb4bd608680, 
request=0x7fb4a8359040, level=0) at ../src/jrd/jrd.cpp:7342
#6  0x7fb4bf286127 in close_cursor (tdbb=0x7fb4bd608680, 
request=0x7fb4a86fcd78) at ../src/dsql/dsql.cpp:925
#7  0x7fb4bf287c68 in DSQL_free_statement (tdbb=0x7fb4bd608680, 
request=0x7fb4a86fcd78, option=1) at ../src/dsql/dsql.cpp:572
#8  0x7fb4bf1d9487 in TRA_release_transaction (tdbb=0x7fb4bd608680, 
transaction=0x7fb4b4ecca48, trace=0x7fb4bd6082b0) at ../src/jrd/tra.cpp:1364
#9  0x7fb4bf1d9d71 in TRA_rollback (tdbb=0x7fb4bd608680, 
transaction=0x7fb4b4ecca48, retaining_flag=false, force_flag=false) at 
../src/jrd/tra.cpp:1532
#10 0x7fb4bf15401c in rollback (tdbb=0x7fb4bd608680, transaction=, retaining_flag=false) at ../src/jrd/jrd.cpp:5852
#11 0x7fb4bf1541a6 in JRD_rollback_transaction (tdbb=0x7fb4bc1ff188, 
transaction=0x7fb4bd60abb8) at ../src/jrd/jrd.cpp:7140
#12 0x7fb4bf155b11 in jrd8_rollback_transaction 
(user_status=0x7fb4bd608910, tra_handle=0x7fb4bd60abb8) at 
../src/jrd/jrd.cpp:3251
#13 0x7fb4bf01e79e in isc_rollback_transaction (user_status=, tra_handle=0x7fb4bc1ff290) at ../src/jrd/why.cpp:4491
#14 0x7fb4bf35a499 in rem_port::disconnect (this=0x7fb4bd611a08, 
sendL=0x7fb4bc1f8208, receiveL=0x7fb4bc1f8630) at ../src/remote/server.cpp:1776
#15 0x7fb4bf35d9a2 in process_packet (port=0x7fb4bd611a08, 
sendL=0x7fb4bc1f8208, receive=0x7fb4bc1f8630, result=0x7fb4bd608e28) at 
../src/remote/server.cpp:3604
#16 0x7fb4bf35f177 in loopThread () at ../src/remote/server.cpp:5289
#17 0x7fb4bf011e50 in run (arg=0x7fb4a37c66c8) at 
../src/jrd/ThreadStart.cpp:128
#18 (anonymous namespace)::threadStart (arg=0x7fb4a37c66c8) at 
../src/jrd/ThreadStart.cpp:139
#19 0x7fb4bdfd9aa1 in start_thread () from /lib64/libpthread.so.0
#20 0x7fb4bdd26bcd in clone () from /lib64/libc.so.6


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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Reopened: (CORE-5652) Rolling back a transaction that creates a function or procedure keeps a cached version of that function or procedure when subsequently re-creating i

[Vlad Khorsun (JIRA)]

 [ 
http://tracker.firebirdsql.org/browse/CORE-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Khorsun reopened CORE-5652:



I missed that script was executed with FlameRobin.
Now, with isql and AUTODDL OFF

SQL>
SQL> SET AUTODDL OFF;
SQL>
SQL> SET TERM ^ ;
SQL> CREATE FUNCTION fnTest ()
CON> RETURNS INTEGER
CON> AS
CON> BEGIN
CON> RETURN 1;
CON> END^
SQL> SET TERM ;^
SQL>
SQL> SELECT fnTest() FROM RDB$DATABASE;

  FNTEST

   1

SQL> ROLLBACK;
SQL> SELECT fnTest() FROM RDB$DATABASE;

  FNTEST

   1

SQL> DROP FUNCTION fnTest;
Statement failed, SQLSTATE = 42000
unsuccessful metadata update
-DROP FUNCTION FNTEST failed
-Function FNTEST not found
SQL>exit;

connect again:

SQL> SELECT fnTest() FROM RDB$DATABASE;
Statement failed, SQLSTATE = 39000
Dynamic SQL Error
-SQL error code = -804
-Function unknown
-FNTEST
SQL>

> Rolling back a transaction that creates a function or procedure keeps a 
> cached version of that function or procedure when subsequently re-creating it.
> --
>
> Key: CORE-5652
> URL: http://tracker.firebirdsql.org/browse/CORE-5652
> Project: Firebird Core
>  Issue Type: Bug
>  Components: Engine
>Affects Versions: 3.0.2
> Environment: Windows 7 32-bit running Firebird 3.0.2.32703 executing 
> scripts with FlameRobin 0.9.3.
>Reporter: Ob-serve
>
> 1.  Execute the following test script:
> SET TERM ^ ;
> CREATE FUNCTION fnTest ()
> RETURNS INTEGER
> AS
> BEGIN
> RETURN 1;
> END^
> SET TERM ; ^
> SELECT fnTest() FROM RDB$DATABASE;
> 2. Then rollback the transaction / script.
> 3.. Now execute:
> SET TERM ^ ;
> CREATE FUNCTION fnTest ()
> RETURNS INTEGER
> AS
> BEGIN
> RETURN 2;
> END^
> SET TERM ; ^
> SELECT fnTest() FROM RDB$DATABASE;
> You should find that the value 1 is still returned incorrectly.
> The same is also true for procedures as you can test by running:
> SET TERM ^ ;
> CREATE OR ALTER PROCEDURE spTest
> RETURNS (
> Result INTEGER
> )
> AS
> BEGIN
> :Result = 1;
> SUSPEND;
> END^
> SET TERM ; ^
> SELECT * FROM spTest;
> Rollback the transaction / script.
> Now run:
> SET TERM ^ ;
> CREATE OR ALTER PROCEDURE spTest
> RETURNS (
> Result INTEGER
> )
> AS
> BEGIN
> :Result = 2;
> SUSPEND;
> END^
> SET TERM ; ^
> SELECT * FROM spTest;
> If you disconnect from the database between rollback and running the modified 
> function / procedure then all works correctly.  Suspect there is a compiled / 
> cached version of the function / procedure which is not being cleared 
> correctly on rollback.
> UPDATE 04/12/2017 SIMILAR ISSUE
> --
> 1. Perform an operation on a table that would violate a constraint.
> 2. Note error message involving violation of constraint 'constraint name'.
> 3. Rollback the transaction.
> 4. Drop the constraint
> 5. Perform the same table that would have violated the constraint.
> 6. Note the error message involving violation of constraint 'unknown'.
> If you repeat the procedure but close & re-open the database connection 
> between steps 3 & 4, you'll find that step 5. now completes successfully.

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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5674) Allow unused Common Table Expressions

[Vlad Khorsun (JIRA)]

Allow unused Common Table Expressions
-

 Key: CORE-5674
 URL: http://tracker.firebirdsql.org/browse/CORE-5674
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Reporter: Vlad Khorsun


When fixing bug CORE-1793 unused CTEs was forbidden - it was simplest solution 
to avoid crash in the engine.
Crash happens due to uninitialized input parameters as unused CTE is not 
handled by syntax analyzer at all.
But it is too stong limitation and users complains about it (not often but 
anyway).

Improvement is to allow queries with unused CTEs and convert error "CTE "XXX" 
is not used in query" into warning.

Also, it will handle unused CTEs by syntax analyzer and catch all errors, for 
example

WITH RECURSIVE
  X AS (SELECT R.RDB$RELATION_NAME FROM RDB$RELATIONS1 R WHERE 
R.RDB$RELATION_ID = 1),
  Y AS (SELECT R.RDB$RELATION_NAME FROM RDB$RELATIONS R WHERE R.RDB$RELATION_ID 
= :ID2)
SELECT * FROM Y

currently works despite of reference on non-existing table RDB$RELATIONS1 in 
CTE X


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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5660) Make flash of big number of dirty pages faster

[Vlad Khorsun (JIRA)]

Make flash of big number of dirty pages faster
--

 Key: CORE-5660
 URL: http://tracker.firebirdsql.org/browse/CORE-5660
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Affects Versions: 4.0 Alpha 1, 3.0.2, 2.5.7, 3.0.1, 2.5.6, 3.0.0, 4.0 
Initial, 2.5.5, 2.5.4, 2.5.3 Update 1, 2.1.7, 2.5.3, 2.5.2 Update 1, 2.5.2, 
2.5.1, 2.5.0
Reporter: Vlad Khorsun


Flush cache algorithm could be improved for the case when there is a big number 
of dirty pages to write.
Current algorithm adds noticeable CPU load and makes whole process slower than 
it could be.

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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5648) Avoid serialization of isc_attach_database calls issued by EXECUTE STATEMENT implementation

[Vlad Khorsun (JIRA)]

Avoid serialization of isc_attach_database calls issued by EXECUTE STATEMENT 
implementation
---

 Key: CORE-5648
 URL: http://tracker.firebirdsql.org/browse/CORE-5648
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Affects Versions: 4.0 Alpha 1, 3.0.2, 2.5.7, 3.0.1, 2.5.6, 3.0.0, 4.0 
Initial, 2.5.5, 2.5.4, 2.1.7, 2.5.3, 2.5.2 Update 1, 2.5.2, 2.5.1, 2.5.0
 Environment: Super Server and Super Classic architectures. 
Classic is not affected.
Reporter: Vlad Khorsun


When EXECUTE STATEMENT ... ON EXTERNAL DATA SOURCE was introiduced in v2.5.0 
there was informal agreement that calls of 
isc_attach_database should be serialized to avoid deadlocks in fbclient 
(reported by users from time to time, but never reproduced).
Such serialization is almost not visible by end users when all works as 
expected, in particular when remote hosts can be reached via network.
But when there is some network issues, or when remote address is not available 
there could be significant delays before isc_attach_database 
returns corresponding error. Due to serialization of call of 
isc_attach_database by the engine all other attachments running EXECUTE 
STATEMENT 
and connecting to the their remote databases should wait for the unlucky one.

Starting from v3 it seems we can remove this artificial limitation in the 
engine and allow all attachments to call isc_attach_database 
in parallel without serialization.

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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5614) Physical backup merge stage could run too long, especially with huge page cache

[Vlad Khorsun (JIRA)]

Physical backup merge stage could run too long, especially with huge page cache
---

 Key: CORE-5614
 URL: http://tracker.firebirdsql.org/browse/CORE-5614
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Affects Versions: 4.0 Alpha 1, 3.0.2, 3.0.1, 3.0.0
Reporter: Vlad Khorsun




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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5613) SuperServer could hung when changing physical backup state under high load

[Vlad Khorsun (JIRA)]

SuperServer could hung when changing physical backup state under high load
--

 Key: CORE-5613
 URL: http://tracker.firebirdsql.org/browse/CORE-5613
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 4.0 Alpha 1, 3.0.2, 3.0.1, 3.0.0
Reporter: Vlad Khorsun


The issue was detected when testing nbackup during TPCC run with 64 concurrent 
connections.
Engine could hung immediately after begin\end backup, i.e. after physical state 
change.
Few threads waits infinitely in RWLock::beginRead() for 
BackupManager::localStateLock.
Wait can't succeed as there is no owner of localStateLock.
Also, lock value is -1 which should never happens.
All other threads waits for bdb latches already acquired by threads above.

The problem happens because of race condition: 

- backup thread acquires localStateLock in Write mode (see 
BackupManager::StateWriteGuard) and set TDBB_backup_write_locked flag (see 
BackupManager::lockStateWrite), 
then it marks header page and set BDB_nbak_state_lock flag on its BufferDesc
note, this mark does not acquire localStateLock in Read mode because of 
BDB_nbak_state_lock (see CCH\set_diff_page() and BackupManager::lockStateRead)
then backup thread release header page (it does not release localStateLock)

- another thread commits and flush dirty pages, it writes dirty header page and 
release localStateLock (see CCH\clear_dirty_flag_and_nbak_state)
as BufferDesc have BDB_nbak_state_lock flag set and tdbb is not marked with 
TDBB_backup_write_locked flag

- backup thread release localStateLock in Write mode (see ~StateWriteGuard) 

I.e. we have excess RWLock::endRead call which broke lock state and leads to 
the hangup.

To make problem happens there should be very short transactions to fit (from 
start to finish) into small time window
between release of header page and localStateLock by backup thread.


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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5582) Segmentation fault in TRA_detach_request

[Vlad Khorsun (JIRA)]

Segmentation fault in TRA_detach_request


 Key: CORE-5582
 URL: http://tracker.firebirdsql.org/browse/CORE-5582
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 2.5.7
 Environment: Linux, CS
Reporter: Vlad Khorsun


There is user report that some of many Firebird CS processes crashes when 
database is shutting down by DBA before sweep run.
The crashes relatively rare, once per few days or weeks.
The coredump contains following stack

#0  0x7f7f438c5d44 in TRA_detach_request (request=0x7f7f34a1dab0) at 
../src/jrd/tra.cpp:208
#1  0x7f7f4380c30e in EXE_unwind (tdbb=0x7f7f41cfdb40, 
request=0x7f7f34a1dab0) at ../src/jrd/exe.cpp:1122
#2  0x7f7f437d5e44 in CMP_release (tdbb=0x7f7f41cfdb40, 
request=0x7f7f34a1dab0) at ../src/jrd/cmp.cpp:2483
#3  0x7f7f437d6ab0 in CMP_fini (tdbb=0x7f7f41cfdb40) at 
../src/jrd/cmp.cpp:743
#4  0x7f7f43843c7d in shutdown_database (dbb=0x7f7f39f89d98, 
release_pools=true) at ../src/jrd/jrd.cpp:5953
#5  0x7f7f43847d41 in purge_attachment (tdbb=0x7f7f41cfdb40, 
attachment=0x7f7f39f83408, force_flag=true) at ../src/jrd/jrd.cpp:6458
#6  0x7f7f438537d2 in jrd8_detach_database (user_status=0x7f7f41cfdd70, 
handle=0x7f7f405d02b8) at ../src/jrd/jrd.cpp:2499
#7  0x7f7f4370edd8 in fb_ping (user_status=, 
db_handle=) at ../src/jrd/why.cpp:6119
#8  0x7f7f43842cba in (anonymous namespace)::attachmentShutdownThread 
(arg=) at ../src/jrd/jrd.cpp:7503
#9  0x7f7f43706f10 in run (arg=0x7f7f2930a138) at 
../src/jrd/ThreadStart.cpp:128
#10 (anonymous namespace)::threadStart (arg=0x7f7f2930a138) at 
../src/jrd/ThreadStart.cpp:139
#11 0x7f7f426ceaa1 in start_thread () from /lib64/libpthread.so.0
#12 0x7f7f4241bbcd in clone () from /lib64/libc.so.6

Coredump analisys show that system request (used in METD to query metadata) 
contains reference  (req_transaction) to the 
(most probably) already deallocated transaction. 


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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5530) Random AV at client application using events when connection was broken

[Vlad Khorsun (JIRA)]

Random AV at client application using events when connection was broken
---

 Key: CORE-5530
 URL: http://tracker.firebirdsql.org/browse/CORE-5530
 Project: Firebird Core
  Issue Type: Bug
  Components: API / Client Library
Affects Versions: 2.5.7, 2.5.6, 2.5.5, 2.5.4, 2.5.3 Update 1, 2.1.7, 2.5.3, 
2.5.2 Update 1, 2.5.2, 2.5.1, 2.5.0
Reporter: Vlad Khorsun


If client application 
- uses local (stack based) status vector when call ISC API functions, and 
- uses events, and
- connection with server is broken,
then random AV could happens in some of application thread's.

The reason is that fbclient saves pointer to the user status-vector at entry to 
the 
all ISC API functions and later report network error happens at event listener 
thread
using that saved pointer to the status-vector. If stack variable is out of 
scope it
means events listener thread wrote to the some "random" place at the stack of
another thread.

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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5522) Engine could freeze up to 2 minutes and raise deadlock error when updating RDB$INDICES if it contains backversions

[Vlad Khorsun (JIRA)]

Engine could freeze up to 2 minutes and raise deadlock error when updating 
RDB$INDICES if it contains backversions 
---

 Key: CORE-5522
 URL: http://tracker.firebirdsql.org/browse/CORE-5522
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 2.5.7
Reporter: Vlad Khorsun


Test case

1. create backversions in rdb$indices and make hard rollback to leave it on 
disk:

delete from t_tx;
insert into t_tx select 1 from rdb$types, rdb$types;
insert into t_tx select 1 from rdb$types, rdb$types;
update rdb$indices set rdb$index_inactive = -1;
quit;

2. Try to set stats for all indices:
update rdb$indices set rdb$index_inactive = -1;

Statement failed, SQLSTATE = 40001
deadlock


Call stack
>   fb_inet_server.exe!latch_bdb(tdbb=0x035cf4d4, type=LATCH_exclusive, 
> bdb=0x043a1478, page={...}, latch_wait=1)  Line 5464C++
fb_inet_server.exe!get_buffer(tdbb=0x035cf4d4, page={...}, 
latch=LATCH_exclusive, latch_wait=1)  Line 4872  C++
fb_inet_server.exe!CCH_fetch_lock(tdbb=0x035cf4d4, window=0x044d8c10, 
lock_type=6, wait=1, page_type='')  Line 889  C++
fb_inet_server.exe!CCH_FETCH_LOCK(tdbb=0x035cf4d4, window=0x044d8c10, 
lock_type=6, wait=1, page_type='')  Line 91   C++
fb_inet_server.exe!CCH_handoff(tdbb=0x035cf4d4, window=0x044d8c10, 
page=85, lock=6, page_type='', latch_wait=1, release_tail=false)  Line 1618  C++
fb_inet_server.exe!CCH_HANDOFF(tdbb=0x035cf4d4, window=0x044d8c10, 
page=85, lock=6, page_type='')  Line 121 C++
fb_inet_server.exe!DPM_get(tdbb=0x035cf4d4, rpb=0x044d8bb8, 
lock_type=6)  Line 1449 C++
fb_inet_server.exe!VIO_backout(tdbb=0x035cf4d4, rpb=0x044d8bb8, 
transaction=0x0338796c)  Line 406   C++
fb_inet_server.exe!VIO_chase_record_version(tdbb=0x035cf4d4, 
rpb=0x044d8bb8, transaction=0x0338796c, pool=0x044d9ea0, writelock=false)  Line 
859C++
fb_inet_server.exe!VIO_get(tdbb=0x035cf4d4, rpb=0x044d8bb8, 
transaction=0x0338796c, pool=0x044d9ea0)  Line 1871 C++
fb_inet_server.exe!get_record(tdbb=0x035cf4d4, rsb=0x044d82ac, 
parent_rsb=0x044d824c, mode=RSE_get_forward)  Line 1887  C++
fb_inet_server.exe!get_record(tdbb=0x035cf4d4, rsb=0x044d824c, 
parent_rsb=0x, mode=RSE_get_forward)  Line 2156  C++
fb_inet_server.exe!fetch_record(tdbb=0x035cf4d4, rsb=0x044d837c, n=0)  
Line 775 C++
fb_inet_server.exe!get_record(tdbb=0x035cf4d4, rsb=0x044d837c, 
parent_rsb=0x, mode=RSE_get_forward)  Line 2339  C++
fb_inet_server.exe!RSE_get_record(tdbb=0x035cf4d4, rsb=0x044d837c, 
mode=RSE_get_forward)  Line 312  C++
fb_inet_server.exe!EXE_looper(tdbb=0x035cf4d4, request=0x044d8830, 
in_node=0x044da180)  Line 1989   C++
fb_inet_server.exe!looper_seh(tdbb=0x035cf4d4, request=0x044d8830, 
node=0x044da180)  Line 2917  C++
fb_inet_server.exe!execute_looper(tdbb=0x035cf4d4, request=0x044d8830, 
transaction=0x0338796c, node=0x044da180, next_state=req_proceed)  Line 1369 
 C++
fb_inet_server.exe!EXE_send(tdbb=0x035cf4d4, request=0x044d8830, msg=0, 
length=32, buffer=0x035ce944)  Line 971 C++
fb_inet_server.exe!MET_lookup_partner(tdbb=0x035cf4d4, 
relation=0x03385490, idx=0x035cea54, index_name=0x)  Line 3796   C++
fb_inet_server.exe!IDX_modify_flag_uk_modified(tdbb=0x035cf4d4, 
org_rpb=0x044cb9d8, new_rpb=0x044cba48, transaction=0x0441c008)  Line 1699  
C++
fb_inet_server.exe!VIO_modify(tdbb=0x035cf4d4, org_rpb=0x044cb9d8, 
new_rpb=0x044cba48, transaction=0x0441c008)  Line 2509   C++
fb_inet_server.exe!modify(tdbb=0x035cf4d4, node=0x044cc3a0, 
which_trig=0)  Line 3008C++
fb_inet_server.exe!EXE_looper(tdbb=0x035cf4d4, request=0x044cb650, 
in_node=0x044cbf84)  Line 2564   C++


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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5507) Wrong value of the new field at the old records, created before that new field was added.

[Vlad Khorsun (JIRA)]

Wrong value of the new field at the old records, created before that new field 
was added.
-

 Key: CORE-5507
 URL: http://tracker.firebirdsql.org/browse/CORE-5507
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.2
Reporter: Vlad Khorsun


RECREATE TABLE T (ID INT NOT NULL, DESCR VARCHAR(32) NOT NULL);
COMMIT;

INSERT INTO T (ID, DESCR) VALUES (1, 'No F1 field');
COMMIT;

ALTER TABLE T ADD F1 VARCHAR(16) DEFAULT 'XYZ' NOT NULL;
COMMIT;

INSERT INTO T (ID, DESCR) VALUES (2, 'F1 field, default XYZ');
COMMIT;

SELECT * FROM T;
COMMIT;

ALTER TABLE T ALTER COLUMN F1 SET DEFAULT 'ABC';
COMMIT;

INSERT INTO T (ID, DESCR) VALUES (3, 'F1 field, default ABC');
COMMIT;

SELECT * FROM T;
COMMIT;


After the first select all is as expected:

  ID DESCRF1
  
   1 No F1 field  XYZ
   2 F1 field, default XYZXYZ

after the second select
expected

  ID DESCRF1
  
   1 No F1 field  ABC
   2 F1 field, default XYZXYZ
   3 F1 field, default ABCABC

actual

  ID DESCRF1
  
   1 No F1 field  XYZ
   2 F1 field, default XYZXYZ
   3 F1 field, default ABCABC

Note value of the field F1 at the first record: it is expected that is should 
be the same as latest DEFAULT value.
Also note that 2nd and 3rd INSERTs assigns correct value to the omitted field - 
same as latest DEFAULT value.


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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5488) Timeouts for running SQL statements and idle connections

[Vlad Khorsun (JIRA)]

Timeouts for running SQL statements and idle connections


 Key: CORE-5488
 URL: http://tracker.firebirdsql.org/browse/CORE-5488
 Project: Firebird Core
  Issue Type: New Feature
  Components: API / Client Library, Engine
Reporter: Vlad Khorsun


Allows to set timeout for SQL statement, i.e. it allows to automatically stop 
execution of SQL statement when it running longer than given timeout value. 
Allows to automatically close user connection after period of inactivity.
More details in 
doc\README.session_idle_timeouts
doc\README.statement_timeouts


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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5464) AV in fbclient when reading blob stored in incompatible encoding

[Vlad Khorsun (JIRA)]

AV in fbclient when reading blob stored in incompatible encoding


 Key: CORE-5464
 URL: http://tracker.firebirdsql.org/browse/CORE-5464
 Project: Firebird Core
  Issue Type: Bug
  Components: API / Client Library
Affects Versions: 3.0.1, 4.0 Initial
Reporter: Vlad Khorsun


firebird>chcp 1251
Active code page: 1251

firebird>isql -ch win1251
Use CONNECT or CREATE DATABASE to specify a database
SQL> create database 'inet://c:\temp\blf.fdb' default character set win1251;
SQL> create domain d_int int;
SQL> comment on domain d_int is 'я пишу кириллицей';
SQL> commit;
SQL> SELECT RDB$FIELD_NAME, RDB$SYSTEM_FLAG, RDB$DESCRIPTION  FROM RDB$FIELDS 
where RDB$DESCRIPTION is not null;

RDB$FIELD_NAME  RDB$SYSTEM_FLAG   RDB$DESCRIPTION
=== === =
D_INT 0   0:3
==
RDB$DESCRIPTION:
я пишу кириллицей
==

SQL> exit;

Now connect using incompatible with WIN1251 encoding and try to read domain 
description:

firebird>isql inet://c:\temp\blf.fdb -ch win1250
Database: inet://c:\temp\blf.fdb, User: SYSDBA
SQL> SELECT RDB$FIELD_NAME, RDB$SYSTEM_FLAG, RDB$DESCRIPTION  FROM RDB$FIELDS 
where RDB$DESCRIPTION is not null;

isql is crashed at this point


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

   

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5441) Cache physical numbers of often used data pages to reduce number of fetches of pointer pages

[Vlad Khorsun (JIRA)]

Cache physical numbers of often used data pages to reduce number of fetches of 
pointer pages


 Key: CORE-5441
 URL: http://tracker.firebirdsql.org/browse/CORE-5441
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Reporter: Vlad Khorsun


When engine need to fetch some data page by its logical number (sequence number 
of DP in relation) it should fetch corresponding PP 
first and look for slot with physical number of given DP. I.e. engine always 
needs to do two fetches from the page cache to read any row.
Cost of page fetch is small (ideally 2 CAS instructions) but not zero, 
especially in highly loaded multy-CPU environment. Also, pointer
pages is a very "hot" pages and many readers could force writers to wait. 
Note, mapping of logical data page number to physical numbers is more-or-less 
stable. 
Obviously, caching of that mapping information could reduce number of fetches 
of PP and lower contention in page cache.

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



--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5434) Read-only transactions in SuperServer could not write Header and TIP pages immediately after edit

[Vlad Khorsun (JIRA)]

Read-only transactions in SuperServer could not write Header and TIP pages 
immediately after edit
-

 Key: CORE-5434
 URL: http://tracker.firebirdsql.org/browse/CORE-5434
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Reporter: Vlad Khorsun


Currently engine writes contents of Header and TIP pages to disk immediately 
after any change (for ex. transaction start increments value of "Next 
transaction" counter, commit changes transaction state etc).
I.e. Header and TIP pages are written to disk not waiting for commit (flush).
This was done by at least two major reasons:
a) safety
b) in CS (and SC) page locks for Header and TIP pages is released immediately 
after use to avoid AST overhead

In the case of many light read-only transactions these writes makes almost 100% 
of whole transaction time.

Since read-only transactions does not change data it is safe to update on disk 
contents of Header and TIP pages 
somewhat later, for example when write transaction started (or committed) or 
when whole page cache is flushed
at database shutdown.

Note, reason (b) doesn't affect SuperServer.

So, improvement is that read-only transaction will not force write of 
Header\TIP page content to disk immediately after change 
(in SS mode, of course). In the case of many light read-only transactions it 
gives significant performance gain.

PS to address this issue in CS mode there is more complex solution, probably it 
will be implemented in v4 a bit later


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



--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5417) Engine could hang up if auto-sweep is starting while database is shuttign down

[Vlad Khorsun (JIRA)]

Engine could hang up if auto-sweep is starting while database is shuttign down
--

 Key: CORE-5417
 URL: http://tracker.firebirdsql.org/browse/CORE-5417
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.1, 2.5.6, 3.0.0, 4.0 Initial
Reporter: Vlad Khorsun


The issue was reported by Jiří Činčura at fb-devel (26 Sep 2016, " Stuck 
transaction in 2.5.6") :

https://sourceforge.net/p/firebird/mailman/message/35391555/


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

   

--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Reopened: (CORE-5257) Enable nested keys in plugin configuration

[Vlad Khorsun (JIRA)]

 [ 
http://tracker.firebirdsql.org/browse/CORE-5257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Khorsun reopened CORE-5257:


Fix Version/s: 3.0.2

Re-opened due to wrong parsing of nested keys

> Enable nested keys in plugin configuration
> --
>
> Key: CORE-5257
> URL: http://tracker.firebirdsql.org/browse/CORE-5257
> Project: Firebird Core
>  Issue Type: Improvement
>  Components: API / Client Library, Engine
>Affects Versions: 3.0.0
>Reporter: Vlad Khorsun
>Assignee: Vlad Khorsun
>Priority: Minor
> Fix For: 4.0 Alpha 1, 3.0.2, 3.0.1
>
>
> Config-parsing code already supports nested keys but this feature is 
> explicitly disabled in code for more than one nesting level.
> API also supports nested keys, see IConfigEntry::getSubConfig method.
> It seems we could safely enable this feature (and there is users asking for 
> it)
> Example of nested keys (could be used in plugins.conf):
> Config = MyPluginConfig {
>   Key1 = Val1
>   Key2 = Val2 {
> SubKey = Val
> Subkey2 = {
> ...
>}
>   }
> }
> currently, such configuration is parsed as set of plain keys.

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



--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5348) Databases created at build process are owned by Windows administrator, not SYSDBA

[Vlad Khorsun (JIRA)]

Databases created at build process are owned by Windows administrator, not 
SYSDBA
-

 Key: CORE-5348
 URL: http://tracker.firebirdsql.org/browse/CORE-5348
 Project: Firebird Core
  Issue Type: Bug
  Components: Build Issues / Porting
Affects Versions: 3.0.0, 4.0 Initial
 Environment: Windows only
Reporter: Vlad Khorsun
Priority: Trivial




-- 
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-5327) internal Firebird consistency check (cannot find tip page (165), file: tra.cpp line: 2307)

[Vlad Khorsun (JIRA)]

internal Firebird consistency check (cannot find tip page (165), file: tra.cpp 
line: 2307)
--

 Key: CORE-5327
 URL: http://tracker.firebirdsql.org/browse/CORE-5327
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.0, 4.0 Initial
Reporter: Vlad Khorsun


Under relatively high load with a lot of UPDATE statements and when records 
gets fragmented too often bugcheck "cannot find tip page" could happens.

Test case was send privately and can't be published, unfortunately.

Test database have page size 16KB and records in test table have near 8KB 
declared length and 1100-1200B packed length, i.e. records fragmented often.


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



--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. http://sdm.link/zohodev2dev
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5302) Performance regression when bulk inserting into table with indices

[Vlad Khorsun (JIRA)]

Performance regression when bulk inserting into table with indices
--

 Key: CORE-5302
 URL: http://tracker.firebirdsql.org/browse/CORE-5302
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.0, 4.0 Initial
Reporter: Vlad Khorsun




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



--
Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5295) Validation could read after the end-of-file when handle multifile database

[Vlad Khorsun (JIRA)]

Validation could read after the end-of-file when handle multifile database
--

 Key: CORE-5295
 URL: http://tracker.firebirdsql.org/browse/CORE-5295
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.0, 4.0 Initial
Reporter: Vlad Khorsun
Priority: Minor


If multifile database have some (non-last) file with size less than maximum 
allowed for this file, engine could attempt to read after the end of such file.
Corresponding code is called by validation only. Database is not corrupted.

Test case
a) make backup
gbak -b EMPLOYEE.FDB EMPLOYEE.FBK

b) restore it into multifile database, make first file big enougth to fit whole 
database
gbak -r -v EMPLOYEE.FBK EMPLOYEE-1.FDB 10 EMPLOYEE-2.FDB
gbak:opened file EMPLOYEE.FBK
gbak:transportable backup -- data in XDR format
gbak:   backup file is compressed
gbak:backup version is 10
gbak:created database EMPLOYEE-1.FDB, page_size 8192 bytes
gbak:started transaction
gbak:adding file EMPLOYEE-2.FDB, starting at page 11
gbak:committing secondary files
...
gbak:finishing, closing, and going home
gbak:adjusting the ONLINE and FORCED WRITES flags

c) validate restored database
gfix -v EMPLOYEE-1.FDB

I/O error during "ReadFile" operation for file "EMPLOYEE-1.FDB"
-Error while trying to read from file
-Reached the end of file

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



--
Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5289) Small memory leak when resultset is empty

[Vlad Khorsun (JIRA)]

Small memory leak when resultset is empty
-

 Key: CORE-5289
 URL: http://tracker.firebirdsql.org/browse/CORE-5289
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.0, 4.0 Initial
Reporter: Vlad Khorsun


Following scenario produced small memory leak at every loop iteration:

isc_dsql_allocate_statement
for (...)
{
  isc_dsql_prepare
  isc_dsql_execute
  isc_dsql_fetch   // returns end-of-stream, i.e. no results
  isc_dsql_free_statement(..., DSQL_unprepare)
}


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



--
Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5257) Enable nested keys in plugin configuration

[Vlad Khorsun (JIRA)]

Enable nested keys in plugin configuration
--

 Key: CORE-5257
 URL: http://tracker.firebirdsql.org/browse/CORE-5257
 Project: Firebird Core
  Issue Type: Improvement
  Components: API / Client Library, Engine
Affects Versions: 3.0.0
Reporter: Vlad Khorsun
Priority: Minor


Config-parsing code already supports nested keys but this feature is explicitly 
disabled in code for more than one nesting level.
API also supports nested keys, see IConfigEntry::getSubConfig method.
It seems we could safely enable this feature (and there is users asking for it)

Example of nested keys (could be used in plugins.conf):

Config = MyPluginConfig {
  Key1 = Val1
  Key2 = Val2 {
SubKey = Val
Subkey2 = {
...
   }
  }
}

currently, such configuration is parsed as set of plain keys.

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



--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5143) GBAK restore failed when there is SQL function accessing table and switch -O(NE_AT_A_TIME) is used

[Vlad Khorsun (JIRA)]

GBAK restore failed when there is SQL function accessing table and switch 
-O(NE_AT_A_TIME) is used
--

 Key: CORE-5143
 URL: http://tracker.firebirdsql.org/browse/CORE-5143
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine, GBAK
Affects Versions: 3.0 RC2
Reporter: Vlad Khorsun
Priority: Minor




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



--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111=/4140
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5140) Wrong error message when user tries to set number of page buffers into not supported value

[Vlad Khorsun (JIRA)]

Wrong error message when user tries to set number of page buffers into not 
supported value
--

 Key: CORE-5140
 URL: http://tracker.firebirdsql.org/browse/CORE-5140
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0 RC2
Reporter: Vlad Khorsun
Priority: Minor


>gfix -b 1 
bad parameters on attach or create database
-Attempt to set in database number of buffers which is out of acceptable range 
[:]

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



--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5110) False FK violation could be reported when attachment used isc_no_garbage_collect flag

[Vlad Khorsun (JIRA)]

False FK violation could be reported when attachment used 
isc_no_garbage_collect flag
-

 Key: CORE-5110
 URL: http://tracker.firebirdsql.org/browse/CORE-5110
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 2.5.5, 3.0 RC1, 3.0 Beta 2, 2.5.4, 2.5.3 Update 1, 3.0 
Beta 1, 2.5.3, 3.0 Alpha 2, 3.0 Alpha 1, 2.5.2 Update 1, 2.5.2, 2.5.1, 2.5.0
Reporter: Vlad Khorsun


isc_dpb_no_garbage_collect flag is respected by constraint checking code and 
false "key violation" error could be reported. 

Possible scenario:

tx1: insert key 1
tx1: rollback
tx2: insert key 1

violation of PRIMARY or UNIQUE KEY constraint

The case was reported by IBPhoenix customer

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



--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5063) Make "show database" command to show numbers of used and free pages in database

[Vlad Khorsun (JIRA)]

Make "show database" command to show numbers of used and free pages in database
---

 Key: CORE-5063
 URL: http://tracker.firebirdsql.org/browse/CORE-5063
 Project: Firebird Core
  Issue Type: Improvement
  Components: ISQL
Affects Versions: 3.0 RC2
Reporter: Vlad Khorsun
Priority: Minor




-- 
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-5033) File fb_user_mapping could be left in Firebird lock directory after correct shutdown of all Firebird worker processes

[Vlad Khorsun (JIRA)]

File fb_user_mapping could be left in Firebird lock directory after correct 
shutdown of all Firebird worker processes
-

 Key: CORE-5033
 URL: http://tracker.firebirdsql.org/browse/CORE-5033
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0 RC 1, 3.0 Beta 2, 3.0 Beta 1
Reporter: Vlad Khorsun
Priority: Minor




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



--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551=/4140
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5034) At least 5 seconds delay on disconnect could happen if disconnect happens close after Event Manager initialization

[Vlad Khorsun (JIRA)]

At least 5 seconds delay on disconnect could happen if disconnect happens close 
after Event Manager initialization
--

 Key: CORE-5034
 URL: http://tracker.firebirdsql.org/browse/CORE-5034
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0 RC 1, 3.0 Beta 2, 3.0 Beta 1
Reporter: Vlad Khorsun
Priority: Minor


Test by Pavel Zotov at CORE-4680 shows the issue very well.
In the test Event Manager initialization happens at ON DISCONNECT trigger 
(which do POST EVENT).

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



--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551=/4140
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5029) AV in fbclient when multi-threaded application uses XNET protocol

[Vlad Khorsun (JIRA)]

AV in fbclient when multi-threaded application uses XNET protocol
-

 Key: CORE-5029
 URL: http://tracker.firebirdsql.org/browse/CORE-5029
 Project: Firebird Core
  Issue Type: Bug
  Components: API / Client Library
Affects Versions: 3.0 RC 1, 3.0 Beta 2, 3.0 Beta 1
 Environment: Windows only
Reporter: Vlad Khorsun




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



--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551=/4140
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-5015) AV in engine could happen when ON DISCONNECT trigger posted event

[Vlad Khorsun (JIRA)]

AV in engine could happen when ON DISCONNECT trigger posted event
-

 Key: CORE-5015
 URL: http://tracker.firebirdsql.org/browse/CORE-5015
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0 RC 1
Reporter: Vlad Khorsun


The test case was provided at CORE-4680

-- 
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-4998) Both client and server could not close connection after failed authentification

[Vlad Khorsun (JIRA)]

Both client and server could not close connection after failed authentification
---

 Key: CORE-4998
 URL: http://tracker.firebirdsql.org/browse/CORE-4998
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0 RC 1
Reporter: Vlad Khorsun


Reported by Dmitry Sibiryakov in fb-devel: "Exit from isql logs INET error on 
Windows after unsuccessful connection attempts" at 6 Nov 2015.
---
after executing following 
script I'm getting in firebird.log number of "INET/inet_error: read errno = 
10054" errors 
equal to number of unsuccessful connection attempts.

connect localhost:test user sysdba password wrong_password;
connect localhost:test user sysdba password another_wrong_password;
connect localhost:test user sysdba password right_password;
exit;
---

The reason for INET errors is that nor client nor server not closed connection 
immediately after 
failure and sockets are closed by OS when isql exits (in this sample).


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



--
Presto, an open source distributed SQL query engine for big data, initially
developed by Facebook, enables you to easily query your data on Hadoop in a 
more interactive manner. Teradata is also now providing full enterprise
support for Presto. Download a free open source copy now.
http://pubads.g.doubleclick.net/gampad/clk?id=250295911=/4140
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Reopened: (CORE-4680) Possible deadlock in firebird connect.

[Vlad Khorsun (JIRA)]

 [ 
http://tracker.firebirdsql.org/browse/CORE-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Khorsun reopened CORE-4680:



I can confirm rare AV's in fbclient but i see no hung of server

> Possible deadlock in firebird connect.
> --
>
> Key: CORE-4680
> URL: http://tracker.firebirdsql.org/browse/CORE-4680
> Project: Firebird Core
>  Issue Type: Bug
>  Components: Engine
>Affects Versions: 3.0 Beta 2
> Environment: Linux / Windows
>Reporter: Sascha Michel
>Priority: Critical
>
> Approximately every month i see a "firebird superserver" that stalled.
> I must restart the server with the init script , every connect to the server 
> is impossible.
> Firebird offers the following message in the log file:
> Koenig_DB_server (Server)   Tue Oct 21 10:47:50 2014
> Shutting down the server with 26 active connection(s) to 1 
> database(s), 0 active service(s)
> Koenig_DB_server (Server)   Thu Nov 13 07:50:54 2014
> Shutting down the server with 16 active connection(s) to 1 
> database(s), 0 active service(s)
> Koenig_DB_server (Server)   Thu Jan 15 09:42:31 2015
> Shutting down the server with 30 active connection(s) to 1 
> database(s), 0 active service(s)
> Koenig_DB_server (Server)   Fri Jan 30 10:24:50 2015
> Shutting down the server with 27 active connection(s) to 1 
> database(s), 0 active service(s)
> Since it was years long so goes, I have written a little program, with which 
> I was able to replicate the problem.
> 1 .A connection is established to the database server 
> 2. 9 events registered. 
> 3. Waited a short time  ( millisecond )
> 4. Unregister the events.
> 5. Connection closed.
> 6. Start all over again.
> If it is possible to kill the process that caused the deadlock, the server 
> continues to run normal.
> If no events were registered it does not happen.
> I was able to reproduce the problem under "super server firebird 2.5 / 3beta2 
>  linux / windows".
> Here's a video that shows that problem.
> https://datiscum.com/FB_Test_x264.mp4
> The program can be downloaded here.
> https://datiscum.com/FirebirdTest.7z
> The downloads are available only for a few days.
> I hope this was helpful and the problem can be eliminated.
> Regards,
>   Sascha Michel

-- 
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-4939) Make IO operations with nbackup backup file aligned at page size boundary

[Vlad Khorsun (JIRA)]

Make IO operations with nbackup backup file aligned at page size boundary
-

 Key: CORE-4939
 URL: http://tracker.firebirdsql.org/browse/CORE-4939
 Project: Firebird Core
  Issue Type: Improvement
  Components: NBACKUP
Reporter: Vlad Khorsun


Currently nbackup backup file contains backup header followed by set of 
 pairs.
Since ODS 12 we store page number at page header. Therefore there is no need to 
store page_number before 
page contents in backup file. Such change makes IO aligned at page size 
boundary which should be more efficient
and opens possibility to work with async\unbuffered IO in the future.

-- 
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-4935) Increase performance of backout of dead record version (or undo of just created primary record version) when backversions chain is too long

[Vlad Khorsun (JIRA)]

Increase performance of backout of dead record version (or undo of just created 
primary record version) when backversions chain is too long
---

 Key: CORE-4935
 URL: http://tracker.firebirdsql.org/browse/CORE-4935
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Affects Versions: 3.0 Beta 2, 2.5.4, 2.5.3 Update 1, 2.1.7, 3.0 Beta 1, 
2.5.3, 2.1.6, 3.0 Alpha 2, 3.0 Alpha 1, 2.5.2 Update 1, 2.1.5 Update 1, 2.5.2, 
2.5.1, 2.5.0
Reporter: Vlad Khorsun


Function list_staying() used in backout and undo processes have complexity 
O(N^2), where N is the number of back versions.

There is a way to reduce complexity down to O(N) in most cases. Specifically - 
when current transaction (which does backout
or undo) already own the record (i.e. primary record version is marked by 
current transaction) there is guarantee that no other
transaction will try to backout\undo the record. 

Another improvement is to cut and cleanup tail of the back-versions chain at 
point where it is legal

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



--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4906) AV when server is shutted down with active trace session(s)

[Vlad Khorsun (JIRA)]

AV when server is shutted down with active trace session(s) 


 Key: CORE-4906
 URL: http://tracker.firebirdsql.org/browse/CORE-4906
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0 Beta 2
Reporter: Vlad Khorsun


1. Run firebird server as application: 
  firebird -a 

2. Start user trace session 
  fbsvcmgr localhost:service_mgr action_trace_start trc_cfg fbtrace1.conf

3. Shutdown firebird server using menu of tray icon

Trace output wiil be like below:
---
Trace session ID 1 started
2015-08-12T15:49:29.0270 (5420:0B6D2790) TRACE_INIT
SESSION_1


Error reading data from the connection.
---

Last line clearly shows that firebird crashed. Tray icon leave at tray and will 
disappear if one try to activate it.



-- 
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] Reopened: (CORE-4876) Named trace session (launched by fbsvcmgr with non-empty value for 'trc_name' parameter) can not be stopped using its name

[Vlad Khorsun (JIRA)]

 [ 
http://tracker.firebirdsql.org/browse/CORE-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Khorsun reopened CORE-4876:


  Assignee: Vlad Khorsun

Sorry, i don't saw error in fbsvcmgr help screen.
Re-opened to fix it.

 Named trace session (launched by fbsvcmgr with non-empty value for 'trc_name' 
  parameter) can not be stopped using its name
 ---

 Key: CORE-4876
 URL: http://tracker.firebirdsql.org/browse/CORE-4876
 Project: Firebird Core
  Issue Type: Bug
  Components: SVCMGR
Reporter: Pavel Zotov
Assignee: Vlad Khorsun

 From the output of 'fbsvcmgr -?' one may see:
 . . .
 action_trace_stop:
 trc_name [string value]
 trc_id [numeric value]
 . . .
 But it seems that we can`t specify key-value pair like 'trc_name 
 my_trace_session' in order to STOP previously launched trace.
 Following is what I did in cmd.exe having prepared trivial config for trace 
 ('tmp_trace.cfg'):
 Step #1
 C:\... start fbsvcmgr localhost:service_mgr user SYSDBA password masterkey 
 action_trace_start trc_cfg .\tmp_trace.cfg  trc_name my_favorite_trace_ssn_01
 // OK, new window will be opened with launched trace session
 Step #2
 C:\... fbsvcmgr localhost:service_mgr user SYSDBA password masterkey 
 action_trace_list
 /*
 Output:
 Session ID: 2
   name:  my_favorite_trace_ssn_01
   user:
   date:  2015-07-15 15:28:52
   flags: active, trace
 */
 Step #3
 C:\... fbsvcmgr localhost:service_mgr user SYSDBA password masterkey 
 action_trace_stop my_favorite_trace_ssn_01
 Error: parameter NAME is incompatible with action STOP
 So, either this option should be excluded from output of fbsvcmgr (and this 
 will be really BAD!) or `action_trace_stop` should be pretty clever to stop 
 trace sessions by their names (and I'm strongly voting for 2nd case :)).

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



--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Reopened: (CORE-4860) Online validation fails on WINDOWS if `dbname` argument contains forward slash ('/') and concurrent attachment which also uses '/' exists.

[Vlad Khorsun (JIRA)]

 [ 
http://tracker.firebirdsql.org/browse/CORE-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vlad Khorsun reopened CORE-4860:


Fix Version/s: 2.5.5

Re-open to backport fix into v2.5

 Online validation fails on WINDOWS if `dbname` argument contains forward 
 slash ('/') and concurrent attachment which also uses '/' exists.
 --

 Key: CORE-4860
 URL: http://tracker.firebirdsql.org/browse/CORE-4860
 Project: Firebird Core
  Issue Type: Bug
Affects Versions: 2.5.4, 3.0 Beta 2
 Environment: Windows XP
Reporter: Pavel Zotov
Assignee: Vlad Khorsun
Priority: Minor
 Fix For: 3.0 RC 1, 2.5.5


 On Windows one may specify FORWARD slash ('/', ascii_char = 47) as subfolders 
 separator in the path to database file, and it works OK:
 C:\FBTESTING\qa\fbt-repoisql 
 localhost/:C:/FBTESTING/qa/fbt-repo/tmp/E30.fdb
 Database:  localhost/:C:/FBTESTING/qa/fbt-repo/tmp/E30.fdb
 But if we do following:
 1) make ISQL connection using this separator (forward slash), 
 2) try to perform online validation using also this separator ('/') in the 
 path to validated database
 -- then we get:
 ===
 fbsvcmgr.exe localhost/:service_mgr user SYSDBA password masterkey 
 action_validate dbname C:/FBTESTING/qa/fbt-repo/tmp/E30.fdb val_lock_timeout 1
 I/O error during CreateFile (open) operation for file 
 C:/FBTESTING/qa/fbt-repo/tmp/E30.fdb
 -Error while trying to open file
 -The process can not access the file because the file is in use by another 
 process.
 ===
 If we change separator in ISQL window to default for Windows (\) than 
 validation works fine.
 If we change separator in fbsvcmgr command line to '\' (but leave '/' in 
 ISQL) than validation also works fine.
 So, the trouble exists only when forward slash is specified both in ISQL 
 connection string and in validation DB path argument.
 BTW: error in FBSVCMGR will not appear for other actions, with forward slash 
 as path separator, e.g.:
 fbsvcmgr.exe localhost/:service_mgr user SYSDBA password masterkey 
 action_db_stats dbname C:/FBTESTING/qa/fbt-repo/tmp/E30.fdb sts_hdr_pages
 -- works OK and produces standard output of DB header info.
 This bug prevent from creating test which tries to validate database online: 
 fbtest engine has $(DATABASE_LOCATION) macro which contains PATH of currently 
 used database. But this macro uses exactly FORWARD slash bot on Linux and 
 Windows as path separator, so one may NOT to do this:
 runProgram('fbsvcmgr',['localhost:service_mgr','user','SYSDBA','password','masterkey','action_validate','dbname','$(DATABASE_LOCATION)bugs.core_4707.fdb','val_lock_timeout','1'])
 -- it will fail with error that is shown above (process can not access the 
 file because the file is in use by another process).

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



--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4867) Server crash when preparing a query with PLAN clause at some CTE

[Vlad Khorsun (JIRA)]

Server crash when preparing a query with PLAN clause at some CTE


 Key: CORE-4867
 URL: http://tracker.firebirdsql.org/browse/CORE-4867
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 2.5.4
Reporter: Vlad Khorsun


1. Prepare metatada:

CREATE TABLE TABLE1 (
  FIELD1 INTEGER NOT NULL
);
ALTER TABLE TABLE1 ADD CONSTRAINT PK_TABLE1 PRIMARY KEY (FIELD1);

CREATE TABLE TABLE2 (
  FIELD1 INTEGER NOT NULL,
  DATE1 DATE NOT NULL
);
ALTER TABLE TABLE2 ADD CONSTRAINT PK_TABLE2 PRIMARY KEY (FIELD1, DATE1)
  USING DESCENDING INDEX PK_TABLE2;
CREATE INDEX IDX_TABLE2 ON TABLE2 (FIELD1, DATE1);
COMMIT;


2. Problem query:
WITH AA
AS (SELECT T1.FIELD1,
   (SELECT FIRST 1 T2.DATE1
  FROM TABLE2 T2
 WHERE T2.FIELD1 = T1.FIELD1
PLAN(T2 INDEX(IDX_TABLE2))
ORDER BY T2.FIELD1 ASC, T2.DATE1 ASC) AS DATE1
  FROM TABLE1 T1)

SELECT DATE1, COUNT('x')
  FROM AA
GROUP BY 1   

Note, if PLAN clause commented out, Firebird will not crash

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



--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4865) Online validation could wrongly report double allocated pages

[Vlad Khorsun (JIRA)]

Online validation could wrongly report double allocated pages
-

 Key: CORE-4865
 URL: http://tracker.firebirdsql.org/browse/CORE-4865
 Project: Firebird Core
  Issue Type: Bug
Affects Versions: 3.0 Beta 2, 2.5.4
Reporter: Vlad Khorsun




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



--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4830) Memory leak in SuperServer

[Vlad Khorsun (JIRA)]

Memory leak in SuperServer
--

 Key: CORE-4830
 URL: http://tracker.firebirdsql.org/browse/CORE-4830
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 2.5.4
 Environment: SuperServer only
Reporter: Vlad Khorsun


Reported by Jojakim Stahl at
https://groups.yahoo.com/neo/groups/firebird-support/conversations/topics/126831

-- 
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-4713) BLOB not found error at rollback after insert into table with expression index

[Vlad Khorsun (JIRA)]

BLOB not found error at rollback after insert into table with expression index


 Key: CORE-4713
 URL: http://tracker.firebirdsql.org/browse/CORE-4713
 Project: Firebird Core
  Issue Type: Bug
Affects Versions: 2.5.3 Update 1, 2.1.7, 3.0 Beta 1, 2.5.3, 2.1.6, 3.0 
Alpha 2, 3.0 Alpha 1, 2.5.2 Update 1, 2.1.5 Update 1, 2.5.2, 2.5.1, 2.5.0
Reporter: Vlad Khorsun


create table T1 (
 ID integer not null,
 N1 blob sub_type text,
);
create index T_IDX on T1 computed by (cast(substring(N1 from 1 for 100) as 
varchar(100)));
commit;

insert into T1 (ID, N1) values (1, 'www');
rollback;

Result:
Unsuccessful execution caused by system error that does not preclude successful 
execution of subsequent statements.
BLOB not found.


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



--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4707) Implement ability to validate tables and indices online (without exclusive access to database)

[Vlad Khorsun (JIRA)]

Implement ability to validate tables and indices online (without exclusive 
access to database)
--

 Key: CORE-4707
 URL: http://tracker.firebirdsql.org/browse/CORE-4707
 Project: Firebird Core
  Issue Type: New Feature
  Components: Engine, SVCMGR
Reporter: Vlad Khorsun


  Database validation allows to run low-level checks of consistency of on-disk 
structures and even to fix some minor corruptions. It is recommended procedure
for any valuable database, i.e. DBA should validate database from time to time
to make sure it is healthy. But validation process requires exclusive access to 
database, i.e. it forbids any kind of concurrent access to database while 
validation run. It could be a big problem to stop user access, especially when 
database is large and validation takes notable amount of time. 

  Online validation is a new feature which allows to perform some consistency
checks without exclusive access to database.

More details will follow in doc/README.online_validation

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



--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4696) No need to flush dirty pages to disk after creation of temporary table index

[Vlad Khorsun (JIRA)]

No need to flush dirty pages to disk after creation of temporary table index


 Key: CORE-4696
 URL: http://tracker.firebirdsql.org/browse/CORE-4696
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Affects Versions: 2.5.3 Update 1, 2.1.7, 3.0 Beta 1, 2.5.3, 2.1.6, 3.0 
Alpha 2, 3.0 Alpha 1, 2.5.2 Update 1, 2.1.5 Update 1, 2.5.2, 2.5.1, 2.5.0
Reporter: Vlad Khorsun
Priority: Minor


When temporary table instance is physically created engine creates also all 
it's indices. 
When index is created and b-tree is fully populated with data engine flushes 
its cache to disk.
It is obviously not needed step when we created (empty) index of temporary 
table instance.


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



--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4688) Recovery after stack overflow exception is not complete

[Vlad Khorsun (JIRA)]

Recovery after stack overflow exception is not complete
---

 Key: CORE-4688
 URL: http://tracker.firebirdsql.org/browse/CORE-4688
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 2.5.3 Update 1, 2.1.7, 3.0 Beta 1, 2.5.3, 2.1.6, 3.0 
Alpha 2, 3.0 Alpha 1, 2.5.2 Update 1, 2.1.5 Update 1, 2.5.2, 2.5.1, 2.5.0
 Environment: WIndows only. On other platforms stack overflow exception 
is not recoverable
Reporter: Vlad Khorsun


We have SEH exceptions handler and convert EXCEPTION_STACK_OVERFLOW into our 
C++ exception. 
This C++ exception correctly handled by our catch blocks.
But there is not call of _resetstkoflw() after error recovery therefore stack 
have no guard page after initial stack overflow and subsequent stack overflow 
lead to AV.

See for details: http://msdn.microsoft.com/en-us/library/89f73td2.aspx

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



--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4627) Deadlock with TIP page lock and monitoring lock

[Vlad Khorsun (JIRA)]

Deadlock with TIP page lock and monitoring lock
---

 Key: CORE-4627
 URL: http://tracker.firebirdsql.org/browse/CORE-4627
 Project: Firebird Core
  Issue Type: Bug
Affects Versions: 2.5.3
Reporter: Vlad Khorsun




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



--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4615) Classic Server could hung with (near) 100% CPU load

[Vlad Khorsun (JIRA)]

Classic Server could hung with (near) 100% CPU load
---

 Key: CORE-4615
 URL: http://tracker.firebirdsql.org/browse/CORE-4615
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 2.5.3, 2.5.2 Update 1, 2.5.2
 Environment: Classic Server\Super Classic
Reporter: Vlad Khorsun


There are few reports from few customers that under some (not very well known) 
conditions Classic Server (or SuperClassic) could 
stop response. At least one process could use almost 100% of CPU (core). Almost 
no IO. The issue is very rare, Firebird could 
work days or weeks without a problem.

Memory dump shows very deep recursive calls of CCH\downgrade() function. 
Sometimes, in SuperClassic we see the cases when 
another thread runs also very deep calls of CCH\write_buffer() function. 

It was never reproduced by me, so i don't know exact reason for this issue. 
There is an idea that while AST thread writes pages and 
cleans dependencies, worker thread doing some work (garbage collection of a 
very long versions chain, for example) and re-creates 
same dependencies, forcing AST thread to clean them again and again.

In attempt to fix it we disabled engine checkouts when thread handles AST 
routine. It makes worker thread to wait while AST is processed.
Must note, that before v2.5 engine always works this way. Customers with 
private build was satisfied and i decided to commit the patch.


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



--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4575) AV in garbage collector thread at disconnect of last attachment

[Vlad Khorsun (JIRA)]

AV in garbage collector thread at disconnect of last attachment
---

 Key: CORE-4575
 URL: http://tracker.firebirdsql.org/browse/CORE-4575
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0 Alpha 2, 3.0 Alpha 1
 Environment: SuperServer only
Reporter: Vlad Khorsun




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



--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4576) Cache Writer thread could not start

[Vlad Khorsun (JIRA)]

Cache Writer thread could not start
---

 Key: CORE-4576
 URL: http://tracker.firebirdsql.org/browse/CORE-4576
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0 Alpha 2, 3.0 Alpha 1
 Environment: SuperServer only
Reporter: Vlad Khorsun




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



--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4570) Wrong error at ALTER PACKAGE

[Vlad Khorsun (JIRA)]

Wrong error at ALTER PACKAGE


 Key: CORE-4570
 URL: http://tracker.firebirdsql.org/browse/CORE-4570
 Project: Firebird Core
  Issue Type: Bug
Affects Versions: 3.0 Alpha 2
Reporter: Vlad Khorsun


1. Create package and its body:

create package p1
as
begin
  function f(x int) returns int;
end

create package body p1
as
begin
  function f1(x int) returns int;

  function f(x int) returns int
  as
  begin
return f1(x) * x;
  end

  function f1(x int) returns int
  as
  begin
 return 1;
  end
end

commit

Result is OK


2. Alter package

alter package p1
as
begin
  function f(x int) returns int;
  function g(x int) returns int;
end
commit

Result is:

This operation is not defined for system tables.
unsuccessful metadata update.
cannot delete.
UDF P1.F1.
there are 1 dependencies.



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



--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4562) Split all validation messages on critical and minor ones

[Vlad Khorsun (JIRA)]

Split all validation messages on critical and minor ones


 Key: CORE-4562
 URL: http://tracker.firebirdsql.org/browse/CORE-4562
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine, GFIX
Reporter: Vlad Khorsun


Some errors reported by database validation (such as orphan pages and few 
another ones) is not critical for database, i.e. not affects query results 
and\or logical consistency of user data.
Such defects should not be counted as errors to not scary users.

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



--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4556) Allocate data pages in group of sequential ordered pages (extents)

[Vlad Khorsun (JIRA)]

Allocate data pages in group of sequential ordered pages (extents)
--

 Key: CORE-4556
 URL: http://tracker.firebirdsql.org/browse/CORE-4556
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Reporter: Vlad Khorsun


DIscussed in fb-devel (see RFC: Data page allocation algorithm at 26 Dec 2013)

I offer to allocate data pages not one-by-one (as currently) but in group 
of sequential ordered pages.
Such group of pages is often called extent. I offer to change page allocation 
algorithm for tables as following:
- if table is empty or small (have no full extent allocated) then data pages is 
allocated one-by-one (as currently)
- if table already have at least one full extent allocated, next request for 
new page will allocate the  whole extent of pages
- size of extent is 8 pages
- every such extent is aligned at 8-pages boundary

Such algoritm will reduce page-level fragmentation (all pages in extent are 
adjacent), allows
OS-level prefetch to work more efficient (it will read not just a bunch of 
pages of random objects but
pages related to the same table) and allows us in the future to read and write 
in a large chunks
making IO more efficient.


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



--
Slashdot TV.  Video for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4510) AV in validation is possible

[Vlad Khorsun (JIRA)]

AV in validation is possible


 Key: CORE-4510
 URL: http://tracker.firebirdsql.org/browse/CORE-4510
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0 Alpha 2, 3.0 Alpha 1
Reporter: Vlad Khorsun


When database physically contains more than pagesPerPIP pages but really used 
is less than pagesPerPIP pages (i.e. second PIP page is not initialized yet) - 
it is possible to get AV on validation.

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



--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4444) Engine could hung and block all attachments in out of disk space condition during physical backup

[Vlad Khorsun (JIRA)]

Engine could hung and block all attachments in out of disk space condition 
during physical backup
-

 Key: CORE-
 URL: http://tracker.firebirdsql.org/browse/CORE-
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0 Alpha 2, 3.0 Alpha 1, 2.5.2 Update 1, 2.1.5 Update 1, 
2.5.2, 2.1.5
Reporter: Vlad Khorsun




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



--
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4443) Use fast file grow on those Linux systems which supports it

[Vlad Khorsun (JIRA)]

Use fast file grow on those Linux systems which supports it
---

 Key: CORE-4443
 URL: http://tracker.firebirdsql.org/browse/CORE-4443
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Reporter: Vlad Khorsun




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



--
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-4445) Extend main database file faster when physical backup state changed from stalled to merge

[Vlad Khorsun (JIRA)]

Extend main database file faster when physical backup state changed from 
stalled to merge
-

 Key: CORE-4445
 URL: http://tracker.firebirdsql.org/browse/CORE-4445
 Project: Firebird Core
  Issue Type: Improvement
  Components: Engine
Reporter: Vlad Khorsun




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



--
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel