Re: Prepared statements versus stored procedures - Mailing list pgsql-general

From David G. Johnston
Subject Re: Prepared statements versus stored procedures
Date
Msg-id CAKFQuwb3Eb_o2wLUoJpQdH+OZnT=gxr5gN1yHftSw1e_jn3sNA@mail.gmail.com
Whole thread Raw
In response to Prepared statements versus stored procedures  (Simon Connah <simon.n.connah@protonmail.com>)
List 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.

pgsql-general by date:

Previous
From: Simon Connah
Date:
Subject: Prepared statements versus stored procedures
Next
From: Francisco Olarte
Date:
Subject: Re: Prepared statements versus stored procedures