79679947

Date: 2025-06-26 05:38:41
Score: 0.5
Natty:
Report link

I encountered the same issue on my DB,

Found the solution to trigger the pruning is doing the conversion using ::timestamp without time zone or with no conversion at all, at planning time postgres is not recognizing the index nor the pruning with different data type

Reasons:
  • Low length (0.5):
  • Has code block (-0.5):
  • Low reputation (0.5):
Posted by: Patrick