From: | Justin Swanhart <greenlion(at)gmail(dot)com> |
---|---|
To: | Simon Connah <simon(at)connah(dot)dev> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Stored procedures or raw queries |
Date: | 2025-08-06 12:07:49 |
Message-ID: | CAJM9iN0YDegRcLG7V6Cv-0pj__B6bB31Of_mp=7RPmdogH6gtw@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Generally you should use stored procedures when it will reduce the number
of round trips to the database. Wrapping simple SELECT statements in a
stored proc just adds friction for updating the application especially as
the number of developers grows.
On Wed, Aug 6, 2025, 8:04 AM Simon Connah <simon(at)connah(dot)dev> wrote:
> Hi,
>
> I'm pretty new to PostgreSQL and am building a simple website with it.
>
> My main question is whether I should use stored procedures / functions
> or whether I should embed raw SQL queries in my backend? I understand
> that procedures are faster as it cuts down on the round trip speed and
> the database can optimise it better.
>
> On the other hand raw SQL is much easier to manage as you just change
> the query in your bankend code without having to apply changes to the
> database at deployment time of your backend.
>
> What is considered the best approach? My backend is written in Go if
> that makes a difference.
>
> If you need any additional information then please let me know.
>
> Simon.
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2025-08-06 12:11:43 | Re: Stored procedures or raw queries |
Previous Message | Simon Connah | 2025-08-06 12:03:41 | Stored procedures or raw queries |