From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | ch(dot)l(dot)ngre(at)online(dot)de |
Subject: | retrieving results of procedures with OUT params |
Date: | 2024-09-02 10:16:06 |
Message-ID: | 172527216699.692.9900337638245208778@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/libpq-exec.html
Description:
https://www.postgresql.org/docs/16/libpq-exec.html#LIBPQ-PQRESULTSTATUS
Existing text:
If the result status is PGRES_TUPLES_OK, PGRES_SINGLE_TUPLE, or
PGRES_TUPLES_CHUNK, then the functions described below can be used to
retrieve the rows returned by the query. Note that a SELECT command that
happens to retrieve zero rows still shows PGRES_TUPLES_OK. PGRES_COMMAND_OK
is for commands that can never return rows (INSERT or UPDATE without a
RETURNING clause, etc.). A response of PGRES_EMPTY_QUERY might indicate a
bug in the client software.
Add:
A successful call to a procedure with OUT parameters will set
PGRES_TUPLES_OK and return one row with the functions described below.
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2024-09-02 21:15:03 | Table rewrite supporting functions for event triggers |
Previous Message | yanliang lei | 2024-09-01 13:38:04 | Re:Re: suggestion about statement_timeout |