The connection order in the WHERE clause of the Oracle Performance Optimization Learning note

Oracle uses a bottom-up sequential parsing where clause, according to which the connection between tables must be written before other where conditions, and those that can filter out the maximum number of records must be written at the end of the WHERE clause.

For example:
(Low efficiency, execution time 156.3 seconds)

SELECT ... From emp ewhere  SAL > 50000AND    JOB = ' MANAGER ' and '    < (SELECT COUNT (*) from EMP             WHERE mgr=e.empno);

(High efficiency, execution time 10.6 seconds)

SELECT ... From EMP Ewhere < (SELECT COUNT (*) from EMP             WHERE mgr=e.empno) and    SAL > 50000AND    JOB = ' MANAGER ';

Small bet
This digest from Baidu Library, specific links to the wood found, sorry.

The connection order in the WHERE clause of the Oracle Performance Optimization Learning note