Re: Prepared statements versus stored procedures

David G. Johnston <david.g.johnston@gmail.com>

From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Simon Connah <simon.n.connah@protonmail.com>
Cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2023-11-19T18:07:38Z
Lists: pgsql-general
On Sun, Nov 19, 2023 at 10:30 AM Simon Connah <simon.n.connah@protonmail.com>
wrote:

> My question is this. If I make a stored procedure doesn't the database
> already pre-plan and optimise the query because it has access to the whole
> query?


No.  Planning isn't about the text of the query, it's about the current
state of the database.

Or could I create a stored procedure and then turn it into a prepared
> statement for more speed?


Not usually.

I was also thinking a stored procedure would help as it requires less
> network round trips as the query is already on the server.
>

Unless your query is insanely large this benefit seems marginal.


> Sorry for the question but I'm not entirely sure how stored procedures and
> prepared statements work together.


They don't.

David J.