Planning with Actual Bind Values
PostgreSQL does not have a shared query plan cache, but it has an optional query plan cache for prepared statements. That means that the developer has the choice to use a prepared statement with or without cached query plan. But note that the cache is dropped when the prepared statement is closed.
The following samples show how to use this functionality in various languages.
The native C API provides the function
PQexecParams, which allows to use bind parameters during prepare (as opposed to
Note that the default setting is five, which means that the first four executions will actually use the bind parameters during prepare, the later ones not. That counter starts fresh for each
There are many frameworks that use a
prepared-statement-cache-sizein the data source setup. That means you can hit limit at any time.