pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra 6+ messages / 1 participants [nested] [flat]
* pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra @ 2023-05-02 21:55 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2023-05-02 21:55 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/66ab2660e0783fd4f6be5936e17a2c8e12335d0d Modified Files -------------- doc/src/sgml/plperl.sgml | 21 ++++++++++++++++----- doc/src/sgml/plpython.sgml | 13 +++++++++++-- doc/src/sgml/pltcl.sgml | 8 +++++--- 3 files changed, 32 insertions(+), 10 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra @ 2023-05-02 21:55 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2023-05-02 21:55 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/b00bae2e9103b4cd4fc97141b3aba2fa0ce532a8 Modified Files -------------- doc/src/sgml/plperl.sgml | 21 ++++++++++++++++----- doc/src/sgml/plpython.sgml | 13 +++++++++++-- doc/src/sgml/pltcl.sgml | 8 +++++--- 3 files changed, 32 insertions(+), 10 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra @ 2023-05-02 21:55 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2023-05-02 21:55 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/825828956ab3c55bd22259d9c480b5f5d2d84416 Modified Files -------------- doc/src/sgml/plperl.sgml | 21 ++++++++++++++++----- doc/src/sgml/plpython.sgml | 13 +++++++++++-- doc/src/sgml/pltcl.sgml | 8 +++++--- 3 files changed, 32 insertions(+), 10 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra @ 2023-05-02 21:55 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2023-05-02 21:55 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/6489875ce6b16662142bc70e003437b9753c199f Modified Files -------------- doc/src/sgml/plperl.sgml | 21 ++++++++++++++++----- doc/src/sgml/plpython.sgml | 13 +++++++++++-- doc/src/sgml/pltcl.sgml | 8 +++++--- 3 files changed, 32 insertions(+), 10 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra @ 2023-05-02 21:55 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2023-05-02 21:55 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_11_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/0e0463fc590c6fe55083ed941e28655bbbb700b4 Modified Files -------------- doc/src/sgml/plperl.sgml | 21 ++++++++++++++++----- doc/src/sgml/plpython.sgml | 13 +++++++++++-- doc/src/sgml/pltcl.sgml | 8 +++++--- 3 files changed, 32 insertions(+), 10 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra @ 2023-05-02 21:55 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2023-05-02 21:55 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/23c7aa865b321b9aba50b105288a5d12ccc35442 Modified Files -------------- doc/src/sgml/plperl.sgml | 21 ++++++++++++++++----- doc/src/sgml/plpython.sgml | 13 +++++++++++-- doc/src/sgml/pltcl.sgml | 8 +++++--- 3 files changed, 32 insertions(+), 10 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2023-05-02 21:55 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2023-05-02 21:55 pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra Tom Lane <tgl@sss.pgh.pa.us> 2023-05-02 21:55 pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra Tom Lane <tgl@sss.pgh.pa.us> 2023-05-02 21:55 pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra Tom Lane <tgl@sss.pgh.pa.us> 2023-05-02 21:55 pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra Tom Lane <tgl@sss.pgh.pa.us> 2023-05-02 21:55 pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra Tom Lane <tgl@sss.pgh.pa.us> 2023-05-02 21:55 pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox