Re: Prepared Statements

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Patrick REED <patrickreed352(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Prepared Statements
Date: 2020-10-02 20:42:47
Message-ID: CAKFQuwZP0szqV5js81E4mKXfs9nWFm7ogJQXuk=X9mcNqoTpfA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 2, 2020 at 1:14 PM Patrick REED <patrickreed352(at)gmail(dot)com>
wrote:

> Hi,
>
> I am having a hard time pinning down which function creates a prepared
> statement.
>
...

> e.g.
> In your favorite language:
>

This doesn't seem like the correct list for this question. Ponder the
following and consider sending any follow-up fresh to the -general list.

The behavior would be specific to "your favorite language" so you should
ask there. Client-side drivers can do lots of things besides interacting
directly with the server.
The docs for the server cover what facilities it provides for handling
prepared statements, both in the protocol [1] and in SQL [2].

You might find that saying why you are investigating this elicits more
helpful responses.

David J.

[1]
https://www.postgresql.org/docs/13/protocol-flow.html#PROTOCOL-FLOW-EXT-QUERY
[2] https://www.postgresql.org/docs/13/sql-prepare.html

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2020-10-02 20:56:20 Re: enable_incremental_sort changes query behavior
Previous Message James Coleman 2020-10-02 20:12:11 Re: enable_incremental_sort changes query behavior