database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-08 11:42:09 +03:00
Code Activity

Fix collection of typos and grammar mistakes in docs and comments

Browse Source 
Author: Justin Pryzby
Discussion: https://postgr.es/m/20190330224333.GQ5815@telsasoft.com
This commit is contained in:
Michael Paquier
2019-04-19 16:57:40 +09:00
parent bc540f9859
commit 148266fa35
6 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/sgml/ecpg.sgml
View File

@ -662,7 +662,7 @@ EXEC SQL DEALLOCATE PREPARE <replaceable>name</replaceable>;
not really useful in real applications. This section explains in not really useful in real applications. This section explains in
detail how you can pass data between your C program and the detail how you can pass data between your C program and the
embedded SQL statements using a simple mechanism called embedded SQL statements using a simple mechanism called
<firstterm>host variables</firstterm>. In an embedded SQL program we <firstterm>host variables</firstterm>. In an embedded SQL program we
consider the SQL statements to be <firstterm>guests</firstterm> in the C consider the SQL statements to be <firstterm>guests</firstterm> in the C
program code which is the <firstterm>host language</firstterm>. Therefore program code which is the <firstterm>host language</firstterm>. Therefore
the variables of the C program are called <firstterm>host the variables of the C program are called <firstterm>host

2
doc/src/sgml/ref/create_index.sgml
View File

@ -181,7 +181,7 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ [ IF NOT EXISTS ] <replaceable class=
</para> </para>
<para> <para>
Currently, the B-tree and the GiST index access methods supports this Currently, the B-tree and the GiST index access methods support this
feature. In B-tree and the GiST indexes, the values of columns listed feature. In B-tree and the GiST indexes, the values of columns listed
in the <literal>INCLUDE</literal> clause are included in leaf tuples in the <literal>INCLUDE</literal> clause are included in leaf tuples
which correspond to heap tuples, but are not included in upper-level which correspond to heap tuples, but are not included in upper-level

2
src/backend/jit/llvm/llvmjit_inline.cpp
View File

@ -9,7 +9,7 @@
* for an external function is found - not guaranteed! - the index will then * for an external function is found - not guaranteed! - the index will then
* be used to judge their instruction count / inline worthiness. After doing * be used to judge their instruction count / inline worthiness. After doing
* so for all external functions, all the referenced functions (and * so for all external functions, all the referenced functions (and
* prerequisites) will be imorted. * prerequisites) will be imported.
* *
* Copyright (c) 2016-2019, PostgreSQL Global Development Group * Copyright (c) 2016-2019, PostgreSQL Global Development Group
* *

2
src/backend/optimizer/plan/planner.c
View File

@ -118,7 +118,7 @@ typedef struct
/* /*
* Temporary structure for use during WindowClause reordering in order to be * Temporary structure for use during WindowClause reordering in order to be
* be able to sort WindowClauses on partitioning/ordering prefix. * able to sort WindowClauses on partitioning/ordering prefix.
*/ */
typedef struct typedef struct
{ {

2
src/backend/utils/hash/dynahash.c
View File

@ -817,7 +817,7 @@ hash_destroy(HTAB *hashp)
{ {
/* allocation method must be one we know how to free, too */ /* allocation method must be one we know how to free, too */
Assert(hashp->alloc == DynaHashAlloc); Assert(hashp->alloc == DynaHashAlloc);
/* so this hashtable must have it's own context */ /* so this hashtable must have its own context */
Assert(hashp->hcxt != NULL); Assert(hashp->hcxt != NULL);
hash_stats("destroy", hashp); hash_stats("destroy", hashp);

2
src/interfaces/libpq/fe-auth.c
View File

@ -879,7 +879,7 @@ pg_fe_sendauth(AuthRequest areq, int payloadlen, PGconn *conn)
case AUTH_REQ_SSPI: case AUTH_REQ_SSPI:
/* /*
* SSPI has it's own startup message so libpq can decide which * SSPI has its own startup message so libpq can decide which
* method to use. Indicate to pg_SSPI_startup that we want SSPI * method to use. Indicate to pg_SSPI_startup that we want SSPI
* negotiation instead of Kerberos. * negotiation instead of Kerberos.
*/ */