pgsql: Fix typos and inconsistencies in code comments

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix typos and inconsistencies in code comments
Date: 2019-06-14 00:41:14
Message-ID: E1hbaHK-00052G-Mv@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix typos and inconsistencies in code comments

Author: Alexander Lakhin
Discussion: https://postgr.es/m/dec6aae8-2d63-639f-4d50-20e229fb83e3@gmail.com

Branch
------
master

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

Modified Files
--------------
src/backend/access/nbtree/nbtsearch.c | 2 +-
src/backend/catalog/catalog.c | 2 +-
src/backend/commands/copy.c | 2 +-
src/backend/libpq/be-secure-gssapi.c | 2 +-
src/backend/parser/parse_target.c | 2 +-
src/backend/postmaster/checkpointer.c | 11 +++++------
src/backend/utils/cache/lsyscache.c | 2 +-
src/port/pg_bitutils.c | 4 ++--
8 files changed, 13 insertions(+), 14 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2019-06-14 02:07:28 pgsql: docs: PG 12 relnotes, move vacuumdb to the client app section
Previous Message Alvaro Herrera 2019-06-14 00:27:30 Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock