pgsql: Improve documentation about behavior of multi-statement Query me

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Improve documentation about behavior of multi-statement Query me
Date: 2017-09-07 18:04:56
Message-ID: E1dq1Ae-00052O-NM@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Improve documentation about behavior of multi-statement Query messages.

We've long done our best to sweep this topic under the rug, but in view
of recent work it seems like it's time to explain it more precisely.
Here's an initial cut at doing that.

Discussion: https://postgr.es/m/0A3221C70F24FB45833433255569204D1F6BE40D@G01JPEXMBYT05

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/b976499480bdbab6d69a11e47991febe53865adc

Modified Files
--------------
doc/src/sgml/libpq.sgml | 4 +-
doc/src/sgml/protocol.sgml | 119 +++++++++++++++++++++++++++++++++++++++++
doc/src/sgml/ref/psql-ref.sgml | 49 +++++++++++++++--
3 files changed, 168 insertions(+), 4 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-09-07 23:41:58 pgsql: Improve performance of get_actual_variable_range with recently-d
Previous Message Peter Eisentraut 2017-09-07 17:59:05 pgsql: Reduce excessive dereferencing of function pointers