Spatial predicates impacts other filter values

Hi
Here is a pretty straightforward SQL query :
```
SELECT d.fidji_valeur_fonciere__integer
FROM dvf.disposition d
WHERE d.fidji_valeur_fonciere__integer < 50000
ORDER BY d.fidji_valeur_fonciere__integer DESC ;
```
with a pretty straightforward result starting with values at 49,999

If I add a spatial filter (either Intersects, Overlaps or contains) I get different results :

```
SELECT d.fidji_valeur_fonciere__integer
FROM dvf.disposition d
WHERE d.fidji_valeur_fonciere__integer < 50000
AND ST_Intersects(ST_MakeEnvelope(1.526264074441798, 45.15464025455313, 1.5394900973676613, 45.16297435294794), d.geom)
ORDER BY d.fidji_valeur_fonciere__integer DESC ;
```

now the results start with a 65500 value, not respecting the d.fidji_valeur_fonciere__integer < 50000 clause.
If I remove the d.fidji_valeur_fonciere__integer < 50000 clause, I have even bigger results as expected.
But it's like using the spatial function thwarts the other filter from being executed totally....