pingcap / pingcap/tidb

Query produces different result after disabling predicate_push_down

Open
#53,365 4 comments 0 reactions 0 assignees View on GitHub
severity/minor sig/execution type/bug
Dominant language
Go
Stars
40.5k
Forks
6.2k
PR merge metrics
PR metrics pending

Description

## Bug Report

Please answer these questions before submitting your issue. Thanks!

### 1. Minimal reproduce step (Required)
```sql
CREATE TABLE t0(c0 SMALLINT NOT NULL , PRIMARY KEY(c0));
insert into t0 values(0);
insert into mysql.opt_rule_blacklist values("predicate_push_down");
admin reload opt_rule_blacklist;
select t0.c0 from t0 where (~ (DATE_FORMAT((false), t0.c0)));
delete from mysql.opt_rule_blacklist;
admin reload opt_rule_blacklist;
select t0.c0 from t0 where (~ (DATE_FORMAT((false), t0.c0)));
```

### 2. What did you expect to see? (Required)
Two queries produce same result;
### 3. What did you see instead (Required)
First query produces:
```sql
MySQL [d1]> select t0.c0 from t0 where (~ (DATE_FORMAT((false), t0.c0)));
+----+
| c0 |
+----+
| 0 |
+----+
1 row in set (0.01 sec)
```
Second query produces:
```sql
MySQL [d1]> select t0.c0 from t0 where (~ (DATE_FORMAT((false), t0.c0)));
Empty set, 1 warning (0.01 sec)
```
### 4. What is your TiDB version? (Required)
release version 8.0.0

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.