pgsql: Doc: improve explanation of how to use our code coverage infrast

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Doc: improve explanation of how to use our code coverage infrast
Date: 2020-10-27 18:31:17
Message-ID: E1kXTkb-0003Js-Ll@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Doc: improve explanation of how to use our code coverage infrastructure.

The reference to running "make coverage" in a subdirectory was a
bit obscure, so clarify what happens when you do that. Do a little
desultory copy-editing, too.

Per a question from Peter Smith.

Discussion: https://postgr.es/m/CAHut+Pu0r3AjRSyu5E0v2-zRj8r24OSrkWs3fEBxOuaw1i8DKA@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/8d132b2850d4c95ed5666a09b295dea645bbc884

Modified Files
--------------
doc/src/sgml/regress.sgml | 21 ++++++++++++++++-----
1 file changed, 16 insertions(+), 5 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2020-10-27 19:37:31 pgsql: Fix use-after-free bug with event triggers and ALTER TABLE.
Previous Message Bruce Momjian 2020-10-27 18:01:00 pgsql: Makefile comment: remove reference to tools/thread/thread_test