| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "Ruslan R(dot) Laishev" <zator(at)yandex(dot)ru> |
| Cc: | pgsql-novice <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: Executing prepared statements in the multithreaded envs |
| Date: | 2017-10-17 15:25:49 |
| Message-ID: | CAKFQuwZ+G5+9sX=f4mMNi8Rh1mOWYc3RHK4Jw2zfppHG_CzD-Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Tue, Oct 17, 2017 at 8:16 AM, Ruslan R. Laishev <zator(at)yandex(dot)ru> wrote:
> A quotation from the docs "for me" :
>
> PQprepare
> Submits a request to create a prepared statement with the given
> parameters, and waits for com-
> pletion.
> PGresult
> * PQprepare(PGconn * conn,
> const char
> * stmtName,
> const char
> * query,
> int nParams,
> const Oid
> * paramTypes);
>
>
The function returns a PGresult so I'd assume you'd handle PQprepare just
like any other result-returning function.
Specifically, "ExecStatusType PQresultStatus(const PGresult *res);" seems
useful.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Froehlich | 2017-10-17 21:32:38 | max_wal_size & compression on compressed filesystem |
| Previous Message | Ruslan R. Laishev | 2017-10-17 15:16:35 | Re: Executing prepared statements in the multithreaded envs |