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 | 825828956ab3c55bd22259d9c480b5f5d2d84416 (patch) | |
| tree | 6e45531c80c8a4d001dbb8888b72ec6177d7d1b9 /src/backend/utils/adt/array_userfuncs.c | |
| parent | 900a8d526ff538d6cd03c3f52ba09fd4dc765915 (diff) | |
| download | postgresql-825828956ab3c55bd22259d9c480b5f5d2d84416.tar.gz postgresql-825828956ab3c55bd22259d9c480b5f5d2d84416.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