not really useful in real applications. This section explains in
detail how you can pass data between your C program and the
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
program code which is the <firstterm>host language</firstterm>. Therefore
the variables of the C program are called <firstterm>host
</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
in the <literal>INCLUDE</literal> clause are included in leaf tuples
which correspond to heap tuples, but are not included in upper-level
* for an external function is found - not guaranteed! - the index will then
* be used to judge their instruction count / inline worthiness. After doing
* 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
*
/*
* 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
{
{
/* allocation method must be one we know how to free, too */
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);
hash_stats("destroy", hashp);
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
* negotiation instead of Kerberos.
*/