|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
W10 x64 FB3 build 32268
|
|
Issue Links:
|
Relate
|
|
This issue relate to:
|
|
CORE-5481
Available indices are not used in some cases if ORDER BY expression is a filtered one
|
|
|
|
|
CORE-5965
FB3 Optimiser chooses less efficient plan than FB2.5 optimiser
|
|
|
|
|
|
|
|
| QA Status: |
Done successfully
|
|
create table test1 (ia integer not null,id integer not null, it integer not null, dt date not null, primary key (ia,id));
create table test2 (ia integer not null, it integer not null, dt date not null, primary key (ia,dt,it));
alter table test1 add CONSTRAINT fk_test2 FOREIGN key (ia,dt,it) REFERENCES test2 (ia,dt,it)
select * from test1
where ia=1 and dt='01/01/2015' and it=1
order by id;
plan : PLAN (TEST1 ORDER RDB$PRIMARY249)
performance very poor
the same problem with :
select id from test1
where ia=1 and dt='01/01/2015' and it=1
group by id
where without order or group works fine
|
|
Description
|
create table test1 (ia integer not null,id integer not null, it integer not null, dt date not null, primary key (ia,id));
create table test2 (ia integer not null, it integer not null, dt date not null, primary key (ia,dt,it));
alter table test1 add CONSTRAINT fk_test2 FOREIGN key (ia,dt,it) REFERENCES test2 (ia,dt,it)
select * from test1
where ia=1 and dt='01/01/2015' and it=1
order by id;
plan : PLAN (TEST1 ORDER RDB$PRIMARY249)
performance very poor
the same problem with :
select id from test1
where ia=1 and dt='01/01/2015' and it=1
group by id
where without order or group works fine |
Show » |
| There are no subversion log entries for this issue yet.
|
|
Bug
