Home/ Questions/Q 6755313
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T13:23:06+00:00

According to PostgreSQL documentation section: 5.9.6. Caveats Constraint exclusion only works when the query’s

  • 0

According to PostgreSQL documentation section: 5.9.6. Caveats

Constraint exclusion only works when the query’s WHERE clause contains
constants. A parametrized query will not be optimized, since the
planner cannot know which partitions the parameter value might select
at run time.

Is there any library that provide some sort of PreparedStatement(I mean only SQL injection facility since we could not benefit from optimized performance of PreparedStatement) and also generates a static SQL string so we could benefit from Constraint Exclusion feature?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You can configure the PostgreSQL JDBC driver to switch over to prepared statements after a certain number of invocations. See Connection to the Database the variable prepareThreshold and also follow the link in that section.

    In your case you can either try the value 0 or a very large number. I’m not sure whether 0 means “use prepared statements immediately” or “never use prepared statements”. A large number should prevent prepared statements for sure.

    Using this method, your Java-code still uses PreparedStatement and the driver is responsible for proper quoting. The protocol between the driver and the server will use “unprepared” statements.

    • 0