spelling: Postgresql -> PostgreSQL

README.unittests.rst

@@ -183,12 +183,12 @@ preexisting tables will interfere with the tests.
 
 Several tests require alternate usernames or schemas to be present, which
 are used to test dotted-name access scenarios.  On some databases such
-as Oracle or Sybase, these are usernames, and others such as Postgresql
+as Oracle or Sybase, these are usernames, and others such as PostgreSQL
 and MySQL they are schemas.   The requirement applies to all backends
 except SQLite and Firebird.  The names are::
 
     test_schema
-    test_schema_2 (only used on Postgresql)
+    test_schema_2 (only used on PostgreSQL)
 
 Please refer to your vendor documentation for the proper syntax to create
 these namespaces - the database user must have permission to create and drop
@@ -335,6 +335,6 @@ For example, to run against sqlite, mysql, postgresql with four processes::
 
     tox -e -- -n 4 --db sqlite --db postgresql --db mysql
 
-Each backend has a different scheme for setting up the database.  Postgresql
+Each backend has a different scheme for setting up the database.  PostgreSQL
 still needs the "test_schema" and "test_schema_2" schemas present, as the
 parallel databases are created using the base database as a "template".

doc/build/changelog/changelog_06.rst

@@ -543,7 +543,7 @@
       of the auto-generated sequence of a SERIAL column,
       which currently only occurs if implicit_returning=False,
       now accommodates if the table + column name is greater
-      than 63 characters using the same logic Postgresql uses.
+      than 63 characters using the same logic PostgreSQL uses.
 
     .. change::
         :tags: postgresql
@@ -2850,7 +2850,7 @@
         :tags: postgresql
         :tickets: 1071
 
-      Postgresql now reflects sequence names associated with
+      PostgreSQL now reflects sequence names associated with
       SERIAL columns correctly, after the name of the sequence
       has been changed.  Thanks to Kumar McMillan for the patch.
 
@@ -2873,7 +2873,7 @@
         :tags: postgresql
         :tickets: 1769
 
-      Postgresql reflects the name of primary key constraints,
+      PostgreSQL reflects the name of primary key constraints,
       if one exists.
 
     .. change::
@@ -3462,7 +3462,7 @@
       as well as the adaptation of the Python operator into
       a SQL operator, based on the full left/right/operator
       of the given expression.  In particular
-      the date/time/interval system created for Postgresql
+      the date/time/interval system created for PostgreSQL
       EXTRACT in has now been generalized into
       the type system.   The previous behavior which often
       occurred of an expression "column + literal" forcing
@@ -4259,7 +4259,7 @@
 
       returning() support is native to insert(), update(),
       delete(). Implementations of varying levels of
-      functionality exist for Postgresql, Firebird, MSSQL and
+      functionality exist for PostgreSQL, Firebird, MSSQL and
       Oracle. returning() can be called explicitly with column
       expressions which are then returned in the resultset,
       usually via fetchone() or first().
@@ -4280,7 +4280,7 @@
       another will now be grouped with parenthesis - previously,
       the first compound element in the list would not be grouped,
       as SQLite doesn't like a statement to start with
-      parenthesis.   However, Postgresql in particular has
+      parenthesis.   However, PostgreSQL in particular has
       precedence rules regarding INTERSECT, and it is
       more consistent for parenthesis to be applied equally
       to all sub-elements.   So now, the workaround for SQLite
@@ -4586,7 +4586,7 @@
 
       The "start" and "increment" attributes on Sequence now
       generate "START WITH" and "INCREMENT BY" by default,
-      on Oracle and Postgresql.  Firebird doesn't support
+      on Oracle and PostgreSQL.  Firebird doesn't support
       these keywords right now.
 
     .. change::
@@ -5279,7 +5279,7 @@
       optimized, resulting in varying speed improvements:
       Unicode, PickleType, Interval, TypeDecorator, Binary.
       Also the following dbapi-specific implementations have been improved:
-      Time, Date and DateTime on Sqlite, ARRAY on Postgresql,
+      Time, Date and DateTime on Sqlite, ARRAY on PostgreSQL,
       Time on MySQL, Numeric(as_decimal=False) on MySQL, oursql and
       pypostgresql, DateTime on cx_oracle and LOB-based types on cx_oracle.
 

doc/build/changelog/changelog_07.rst

@@ -88,7 +88,7 @@
         :tickets: 2676
         :versions: 0.8.0
 
-      Added support for Postgresql's traditional SUBSTRING
+      Added support for PostgreSQL's traditional SUBSTRING
       function syntax, renders as "SUBSTRING(x FROM y FOR z)"
       when regular ``func.substring()`` is used.
       Courtesy Gunnlaugur Þór Briem.
@@ -885,7 +885,7 @@
         :tickets: 2445
 
       Added new for_update/with_lockmode()
-      options for Postgresql: for_update="read"/
+      options for PostgreSQL: for_update="read"/
       with_lockmode("read"),
       for_update="read_nowait"/
       with_lockmode("read_nowait").
@@ -1873,7 +1873,7 @@
       The update() construct can now accommodate
       multiple tables in the WHERE clause, which will
       render an "UPDATE..FROM" construct, recognized by
-      Postgresql and MSSQL.  When compiled on MySQL,
+      PostgreSQL and MSSQL.  When compiled on MySQL,
       will instead generate "UPDATE t1, t2, ..".  MySQL
       additionally can render against multiple tables in the
       SET clause, if Column objects are used as keys
@@ -1968,7 +1968,7 @@
         :tickets: 1679
 
       a "has_schema" method has been implemented
-      on dialect, but only works on Postgresql so far.
+      on dialect, but only works on PostgreSQL so far.
       Courtesy Manlio Perillo.
 
     .. change::
@@ -2025,7 +2025,7 @@
         :tags: postgresql, bug
         :tickets: 2311
 
-      Postgresql dialect memoizes that an ENUM of a
+      PostgreSQL dialect memoizes that an ENUM of a
       particular name was processed
       during a create/drop sequence.  This allows
       a create/drop sequence to work without any
@@ -3696,7 +3696,7 @@
         :tickets: 2081
 
       REAL has been added to the core types.  Supported
-      by Postgresql, SQL Server, MySQL, SQLite.  Note
+      by PostgreSQL, SQL Server, MySQL, SQLite.  Note
       that the SQL Server and MySQL versions, which
       add extra arguments, are also still available
       from those dialects.
@@ -4348,7 +4348,7 @@
         :tickets: 1069
 
       Query.distinct() now accepts column expressions
-      as \*args, interpreted by the Postgresql dialect
+      as \*args, interpreted by the PostgreSQL dialect
       as DISTINCT ON (<expr>).
 
     .. change::
@@ -4448,7 +4448,7 @@
         :tickets: 1069
 
       select.distinct() now accepts column expressions
-      as \*args, interpreted by the Postgresql dialect
+      as \*args, interpreted by the PostgreSQL dialect
       as DISTINCT ON (<expr>).  Note this was already
       available via passing a list to the `distinct`
       keyword argument to select().
@@ -4531,7 +4531,7 @@
       "isolation_level" argument, sets transaction isolation
       level for that connection only until returned to the
       connection pool, for those backends which support it
-      (SQLite, Postgresql)
+      (SQLite, PostgreSQL)
 
     .. change::
         :tags: sql
@@ -4648,7 +4648,7 @@
       of the auto-generated sequence of a SERIAL column,
       which currently only occurs if implicit_returning=False,
       now accommodates if the table + column name is greater
-      than 63 characters using the same logic Postgresql uses. (also in 0.6.7)
+      than 63 characters using the same logic PostgreSQL uses. (also in 0.6.7)
 
     .. change::
         :tags: postgresql
@@ -4668,7 +4668,7 @@
       'unbounded'.  This also occurs for the VARBINARY type..
 
       This behavior makes these types more closely compatible
-      with Postgresql's VARCHAR type which is similarly unbounded
+      with PostgreSQL's VARCHAR type which is similarly unbounded
       when no length is specified.
 
     .. change::

doc/build/changelog/changelog_08.rst

@@ -197,7 +197,7 @@
         :versions: 0.9.4
 
         Fixed regression caused by release 0.8.5 / 0.9.3's compatibility
-        enhancements where index reflection on Postgresql versions specific
+        enhancements where index reflection on PostgreSQL versions specific
         to only the 8.1, 8.2 series again
         broke, surrounding the ever problematic int2vector type.  While
         int2vector supports array operations as of 8.1, apparently it only
@@ -284,8 +284,8 @@
         :tags: postgresql, bug
         :versions: 0.9.3
 
-        Support has been improved for Postgresql reflection behavior on very old
-        (pre 8.1) versions of Postgresql, and potentially other PG engines
+        Support has been improved for PostgreSQL reflection behavior on very old
+        (pre 8.1) versions of PostgreSQL, and potentially other PG engines
         such as Redshift (assuming Redshift reports the version as < 8.1).
         The query for "indexes" as well as "primary keys" relies upon inspecting
         a so-called "int2vector" datatype, which refuses to coerce to an array
@@ -351,10 +351,10 @@
         :tickets: 2291
         :versions: 0.9.3
 
-        Revised this very old issue where the Postgresql "get primary key"
+        Revised this very old issue where the PostgreSQL "get primary key"
         reflection query were updated to take into account primary key constraints
         that were renamed; the newer query fails on very old versions of
-        Postgresql such as version 7, so the old query is restored in those cases
+        PostgreSQL such as version 7, so the old query is restored in those cases
         when server_version_info < (8, 0) is detected.
 
     .. change::
@@ -798,8 +798,8 @@
         :tickets: 2819
         :versions: 0.9.0b1
 
-        Fixed bug where Postgresql version strings that had a prefix preceding
-        the words "Postgresql" or "EnterpriseDB" would not parse.
+        Fixed bug where PostgreSQL version strings that had a prefix preceding
+        the words "PostgreSQL" or "EnterpriseDB" would not parse.
         Courtesy Scott Schaefer.
 
     .. change::
@@ -834,7 +834,7 @@
 
         Added a new flag ``system=True`` to :class:`.Column`, which marks
         the column as a "system" column which is automatically made present
-        by the database (such as Postgresql ``oid`` or ``xmin``).  The
+        by the database (such as PostgreSQL ``oid`` or ``xmin``).  The
         column will be omitted from the ``CREATE TABLE`` statement but will
         otherwise be available for querying.   In addition, the
         :class:`.CreateColumn` construct can be appled to a custom
@@ -942,7 +942,7 @@
         form of a some expressions when referring to the ``.c`` collection
         on a ``select()`` construct, but the ``str()`` form isn't available
         since the element relies on dialect-specific compilation constructs,
-        notably the ``__getitem__()`` operator as used with a Postgresql
+        notably the ``__getitem__()`` operator as used with a PostgreSQL
         ``ARRAY`` element.  The fix also adds a new exception class
         :exc:`.UnsupportedCompilationError` which is raised in those cases
         where a compiler is asked to compile something it doesn't know
@@ -1069,7 +1069,7 @@
         :versions: 0.9.0b1
 
         The behavior of :func:`.extract` has been simplified on the
-        Postgresql dialect to no longer inject a hardcoded ``::timestamp``
+        PostgreSQL dialect to no longer inject a hardcoded ``::timestamp``
         or similar cast into the given expression, as this interfered
         with types such as timezone-aware datetimes, but also
         does not appear to be at all necessary with modern versions
@@ -1103,7 +1103,7 @@
         :versions: 0.9.0b1
 
         Fixed bug where the order of columns in a multi-column
-        Postgresql index would be reflected in the wrong order.
+        PostgreSQL index would be reflected in the wrong order.
         Courtesy Roman Podolyaka.
 
     .. change::
@@ -1167,7 +1167,7 @@
         :tags: feature, postgresql
         :versions: 0.9.0b1
 
-        Support for Postgresql 9.2 range types has been added.
+        Support for PostgreSQL 9.2 range types has been added.
         Currently, no type translation is provided, so works
         directly with strings or psycopg2 2.5 range extension types
         at the moment.  Patch courtesy Chris Withers.
@@ -1463,7 +1463,7 @@
       :tags: bug, postgresql
       :tickets: 2681
 
-      The operators for the Postgresql ARRAY type supports
+      The operators for the PostgreSQL ARRAY type supports
       input types of sets, generators, etc. even when
       a dimension is not specified, by turning the given
       iterable into a collection unconditionally.
@@ -1872,7 +1872,7 @@
       is now copied in all cases when :meth:`.Table.tometadata` happens,
       and if ``inherit_schema=True``, the type will take on the new
       schema name passed to the method.   The ``schema`` is important
-      when used with the Postgresql backend, as the type results in
+      when used with the PostgreSQL backend, as the type results in
       a ``CREATE TYPE`` statement.
 
     .. change::
@@ -2153,7 +2153,7 @@
       The :class:`.Insert` construct now supports multi-valued inserts,
       that is, an INSERT that renders like
       "INSERT INTO table VALUES (...), (...), ...".
-      Supported by Postgresql, SQLite, and MySQL.
+      Supported by PostgreSQL, SQLite, and MySQL.
       Big thanks to Idan Kamara for doing the legwork on this one.
 
       .. seealso::
@@ -2272,7 +2272,7 @@
         :tags: postgresql, feature
         :tickets: 2606
 
-      :class:`.HSTORE` is now available in the Postgresql dialect.
+      :class:`.HSTORE` is now available in the PostgreSQL dialect.
       Will also use psycopg2's extensions if available.  Courtesy
       Audrius Kažukauskas.
 
@@ -3199,7 +3199,7 @@
       the `getitem` operator, i.e. the bracket
       operator in Python.  This is used at first
       to provide index and slice behavior to the
-      Postgresql ARRAY type, and also provides a hook
+      PostgreSQL ARRAY type, and also provides a hook
       for end-user definition of custom __getitem__
       schemes which can be applied at the type
       level as well as within ORM-level custom
@@ -3237,7 +3237,7 @@
       String types.  When present, renders as
       COLLATE <collation>.  This to support the
       COLLATE keyword now supported by several
-      databases including MySQL, SQLite, and Postgresql.
+      databases including MySQL, SQLite, and PostgreSQL.
 
     .. change::
         :tags: change, sql
@@ -3603,7 +3603,7 @@
         :tags: postgresql, feature
         :tickets: 2506
 
-      Added support for the Postgresql ONLY
+      Added support for the PostgreSQL ONLY
       keyword, which can appear corresponding to a
       table in a SELECT, UPDATE, or DELETE statement.
       The phrase is established using with_hint().
@@ -3614,7 +3614,7 @@
         :tickets:
 
       The "ischema_names" dictionary of the
-      Postgresql dialect is "unofficially" customizable.
+      PostgreSQL dialect is "unofficially" customizable.
       Meaning, new types such as PostGIS types can
       be added into this dictionary, and the PG type
       reflection code should be able to handle simple