Query produces different result after disabling predicate_push_down

[Nickelth]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

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:

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:

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

[yibin87]

This differences are introduced by different behaviors of date_format in tidb and tikv. Besides tikv doesn't handle SQL mode well, this will lead to many inconsistency related cases, especially for zeor-date related cases.
For this case, it is too corner and not realistic to pass date_format with bool and int arguemnts.
Set severity to minor.

[yibin87]

/severity minior

[ti-chi-bot]

@yibin87: The label(s) severity/minior cannot be applied, because the repository doesn't have them.

In response to this:

/severity minior

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[yibin87]

/severity minor