for consistency.
If the value written for an element is <literal>NULL</> (in any case
variant), the element is taken to be NULL. The presence of any quotes
or backslashes disables this and allows the literal string value
- <quote>NULL</> to be entered. Also, for backwards compatibility with
+ <quote>NULL</> to be entered. Also, for backward compatibility with
pre-8.2 versions of <productname>PostgreSQL</>, the <xref
linkend="guc-array-nulls"> configuration parameter can be turned
<literal>off</> to suppress recognition of <literal>NULL</> as a NULL.
null values to be entered. However, <productname>PostgreSQL</> versions
before 8.2 did not support null values in arrays, and therefore would
treat <literal>NULL</> as specifying a normal array element with
- the string value <quote>NULL</>. For backwards compatibility with
+ the string value <quote>NULL</>. For backward compatibility with
applications that require the old behavior, this variable can be
turned <literal>off</>.
</para>
Before <productname>PostgreSQL</productname> 8.1, the arguments of the
sequence functions were of type <type>text</>, not <type>regclass</>, and
the above-described conversion from a text string to an OID value would
- happen at run time during each call. For backwards compatibility, this
+ happen at run time during each call. For backward compatibility, this
facility still exists, but internally it is now handled as an implicit
coercion from <type>text</> to <type>regclass</> before the function is
invoked.
Returns the debug <acronym>TTY</acronym> of the connection.
(This is obsolete, since the server no longer pays attention
to the <acronym>TTY</acronym> setting, but the function remains
- for backwards compatibility.)
+ for backward compatibility.)
<synopsis>
char *PQtty(const PGconn *conn);
The default value for <literal>sslmode</> is <literal>prefer</>. As is shown
in the table, this makes no sense from a security point of view, and it only
promises performance overhead if possible. It is only provided as the default
- for backwards compatibility, and is not recommended in secure deployments.
+ for backward compatibility, and is not recommended in secure deployments.
</para>
</sect2>
<replaceable class="parameter">mode</replaceable> is unused and
ignored as of <productname>PostgreSQL</productname> 8.1; however, for
- backwards compatibility with earlier releases it is best to
+ backward compatibility with earlier releases it is best to
set it to <symbol>INV_READ</symbol>, <symbol>INV_WRITE</symbol>,
or <symbol>INV_READ</symbol> <literal>|</> <symbol>INV_WRITE</symbol>.
(These symbolic constants are defined
<para>
Perl passes <productname>PostgreSQL</productname> arrays as a blessed
PostgreSQL::InServer::ARRAY object. This object may be treated as an array
- reference or a string, allowing for backwards compatibility with Perl
+ reference or a string, allowing for backward compatibility with Perl
code written for <productname>PostgreSQL</productname> versions below 9.1 to
run. For example:
roles being used as SQL roles the <literal>INHERIT</> attribute, while
giving roles being used as SQL users the <literal>NOINHERIT</> attribute.
However, <productname>PostgreSQL</productname> defaults to giving all roles
- the <literal>INHERIT</> attribute, for backwards compatibility with pre-8.1
+ the <literal>INHERIT</> attribute, for backward compatibility with pre-8.1
releases in which users always had use of permissions granted to groups
they were members of.
</para>
The <quote>body</quote> of the function definition
specifies the C-language name of the function, which need not be the
same as the name being declared for SQL use.
- (For reasons of backwards compatibility, an empty body
+ (For reasons of backward compatibility, an empty body
is accepted as meaning that the C-language function name is the
same as the SQL name.)
</para>
/*
* OPTIONAL pointer to result slot
*
- * This is obsolete and only present for backwards compatibility, viz,
+ * This is obsolete and only present for backward compatibility, viz,
* user-defined SRFs that use the deprecated TupleDescGetSlot().
*/
TupleTableSlot *slot;