diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2023-05-02 17:55:01 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2023-05-02 17:55:01 -0400 |
| commit | 23c7aa865b321b9aba50b105288a5d12ccc35442 (patch) | |
| tree | 54b4cf483c23167957ffb692966b84bed866d58f /src/backend/utils/adt/array_userfuncs.c | |
| parent | 77ea05406cb61292782eb874866247f20b47b6df (diff) | |
| download | postgresql-23c7aa865b321b9aba50b105288a5d12ccc35442.tar.gz postgresql-23c7aa865b321b9aba50b105288a5d12ccc35442.zip | |
Doc: clarify behavior of row-limit arguments in the PLs' SPI wrappers.
plperl, plpython, and pltcl all provide query-execution functions
that are thin wrappers around SPI_execute() or its variants.
The SPI functions document their row-count limit arguments clearly,
as "maximum number of rows to return, or 0 for no limit". However
the PLs' documentation failed to explain this special behavior of
zero, so that a reader might well assume it means "fetch zero
rows". Improve that.
Daniel Gustafsson and Tom Lane, per report from Kieran McCusker
Discussion: https://postgr.es/m/CAGgUQ6H6qYScctOhktQ9HLFDDoafBKHyUgJbZ6q_dOApnzNTXg@mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/array_userfuncs.c')
0 files changed, 0 insertions, 0 deletions