pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Doc: minor improvements for plpgsql "Transaction Management" sec 2+ messages / 1 participants [nested] [flat]
* pgsql: Doc: minor improvements for plpgsql "Transaction Management" sec @ 2024-07-15 15:59 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 2+ messages in thread From: Tom Lane @ 2024-07-15 15:59 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Doc: minor improvements for plpgsql "Transaction Management" section. Point out that savepoint commands cannot be issued in PL/pgSQL, and suggest that exception blocks can usually be used instead. Add a caveat to the discussion of cursor loops vs. transactions, pointing out that any locks taken by the cursor query will be lost at COMMIT. This is implicit in what's already said, but the existing text leaves the distinct impression that the auto-hold behavior is transparent, which it's not really. Per a couple of recent complaints (one unsigned, and one in bug #18531 from Dzmitry Jachnik). Back-patch to v17, just so this makes it into current docs in less than a year-and-a-half. Discussion: https://postgr.es/m/172076354433.736586.14347210271966220018@wrigleys.postgresql.org Discussion: https://postgr.es/m/18531-c6dddd33b8555fd2@postgresql.org Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/a0899c0a97d19b0c330ff885af4b78b3e7efb100 Modified Files -------------- doc/src/sgml/plpgsql.sgml | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: Doc: minor improvements for plpgsql "Transaction Management" sec @ 2024-07-15 15:59 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 2+ messages in thread From: Tom Lane @ 2024-07-15 15:59 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Doc: minor improvements for plpgsql "Transaction Management" section. Point out that savepoint commands cannot be issued in PL/pgSQL, and suggest that exception blocks can usually be used instead. Add a caveat to the discussion of cursor loops vs. transactions, pointing out that any locks taken by the cursor query will be lost at COMMIT. This is implicit in what's already said, but the existing text leaves the distinct impression that the auto-hold behavior is transparent, which it's not really. Per a couple of recent complaints (one unsigned, and one in bug #18531 from Dzmitry Jachnik). Back-patch to v17, just so this makes it into current docs in less than a year-and-a-half. Discussion: https://postgr.es/m/172076354433.736586.14347210271966220018@wrigleys.postgresql.org Discussion: https://postgr.es/m/18531-c6dddd33b8555fd2@postgresql.org Branch ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/34f457e99a86845e7c1826686921f0daa6a02dfd Modified Files -------------- doc/src/sgml/plpgsql.sgml | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2024-07-15 15:59 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2024-07-15 15:59 pgsql: Doc: minor improvements for plpgsql "Transaction Management" sec Tom Lane <tgl@sss.pgh.pa.us> 2024-07-15 15:59 pgsql: Doc: minor improvements for plpgsql "Transaction Management" sec 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