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 | 66ab2660e0783fd4f6be5936e17a2c8e12335d0d (patch) | |
| tree | 3b46e9d3feac303a0e3e1774451764e130753812 /src/backend/access/gist/gistbuildbuffers.c | |
| parent | 43beaa2fb16b18d3ec0dc385688cff264f6b7364 (diff) | |
| download | postgresql-66ab2660e0783fd4f6be5936e17a2c8e12335d0d.tar.gz postgresql-66ab2660e0783fd4f6be5936e17a2c8e12335d0d.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/access/gist/gistbuildbuffers.c')
0 files changed, 0 insertions, 0 deletions