Skip to content

Commit

Permalink
Release 9.5 (#963)
Browse files Browse the repository at this point in the history
* Bump version

* Uniformly use "current" ver in pg docs links

* Update extension versions on Cloud
  • Loading branch information
jonels-msft committed Nov 12, 2020
1 parent c49a7fb commit 3d620cd
Show file tree
Hide file tree
Showing 16 changed files with 29 additions and 29 deletions.
2 changes: 1 addition & 1 deletion admin_guide/cluster_management.rst
Original file line number Diff line number Diff line change
Expand Up @@ -447,7 +447,7 @@ Resource Conservation
Limiting Long-Running Queries
-----------------------------

Long running queries can hold locks, queue up WAL, or just consume a lot of system resources, so in a production environment it's good to prevent them from running too long. You can set the `statement_timeout <https://www.postgresql.org/docs/10/static/runtime-config-client.html#GUC-STATEMENT-TIMEOUT>`_ parameter on the coordinator and workers to cancel queries that run too long.
Long running queries can hold locks, queue up WAL, or just consume a lot of system resources, so in a production environment it's good to prevent them from running too long. You can set the `statement_timeout <https://www.postgresql.org/docs/current/static/runtime-config-client.html#GUC-STATEMENT-TIMEOUT>`_ parameter on the coordinator and workers to cancel queries that run too long.

.. code-block:: postgres
Expand Down
12 changes: 6 additions & 6 deletions admin_guide/upgrading_citus.rst
Original file line number Diff line number Diff line change
Expand Up @@ -15,21 +15,21 @@ Upgrading the Citus version requires first obtaining the new Citus extension and
Patch Version Upgrade
---------------------

To upgrade a Citus version to its latest patch, issue a standard upgrade command for your package manager. Assuming version 9.4 is currently installed on Postgres 12:
To upgrade a Citus version to its latest patch, issue a standard upgrade command for your package manager. Assuming version 9.5 is currently installed on Postgres 12:

**Ubuntu or Debian**

.. code-block:: bash
sudo apt-get update
sudo apt-get install --only-upgrade postgresql-12-citus-9.4
sudo apt-get install --only-upgrade postgresql-12-citus-9.5
sudo service postgresql restart
**Fedora, CentOS, or Red Hat**

.. code-block:: bash
sudo yum update citus94_12
sudo yum update citus95_12
sudo service postgresql-12 restart
.. _major_minor_upgrade:
Expand All @@ -48,22 +48,22 @@ Each major and minor version of Citus is published as a package with a separate
Step 1. Update Citus Package
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If upgrading both Citus and Postgres, always be sure to upgrade the Citus extension first, and the PostgreSQL version second (see :ref:`upgrading_postgres`). Here is how to do a Citus upgrade from 8.3 to 9.4
If upgrading both Citus and Postgres, always be sure to upgrade the Citus extension first, and the PostgreSQL version second (see :ref:`upgrading_postgres`). Here is how to do a Citus upgrade from 8.3 to 9.5

**Ubuntu or Debian**

.. code-block:: bash
sudo apt-get update
sudo apt-get install postgresql-11-citus-9.4
sudo apt-get install postgresql-11-citus-9.5
sudo service postgresql restart
**Fedora, CentOS, or Red Hat**

.. code-block:: bash
# Fedora, CentOS, or Red Hat
sudo yum swap citus83_11 citus94_11
sudo yum swap citus83_11 citus95_11
sudo service postgresql-11 restart
Step 2. Apply Update in DB
Expand Down
2 changes: 1 addition & 1 deletion articles/parallel_indexing.rst
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Indexes are an essential tool for optimizing database performance and
are becoming ever more important with big data. However, as the volume
of data increases, index maintenance often becomes a write bottleneck,
especially for `advanced index
types <https://www.postgresql.org/docs/9.6/static/textsearch-indexes.html>`__
types <https://www.postgresql.org/docs/current/static/textsearch-indexes.html>`__
which use a lot of CPU time for every row that gets written. Index
creation may also become prohibitively expensive as it may take hours or
even days to build a new index on terabytes of data in PostgreSQL. Citus makes creating and maintaining indexes that much faster through parallelization.
Expand Down
2 changes: 1 addition & 1 deletion articles/semi_structured_data.rst
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ using a
column for url\_params is much more convenient than creating columns for
each parameter. With JSONB we can get both the flexibility of schema,
and combined with `GIN
indexing <https://www.postgresql.org/docs/10/static/gin.html>`__ we can
indexing <https://www.postgresql.org/docs/current/static/gin.html>`__ we can
still have performant queries against all keys and values without having
to index them individually.

Expand Down
4 changes: 2 additions & 2 deletions cloud/additional_extensions.rst
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Generally there is no need to install extensions, however, because every Cloud c
+--------------------+---------+------------+--------------------------------------------------------------------+
| citext | 1.6 | public | data type for case-insensitive character strings |
+--------------------+---------+------------+--------------------------------------------------------------------+
| citus | 9.3-2 | pg_catalog | Citus distributed database |
| citus | 9.4-1 | pg_catalog | Citus distributed database |
+--------------------+---------+------------+--------------------------------------------------------------------+
| cube | 1.4 | public | data type for multidimensional cubes |
+--------------------+---------+------------+--------------------------------------------------------------------+
Expand All @@ -28,7 +28,7 @@ Generally there is no need to install extensions, however, because every Cloud c
+--------------------+---------+------------+--------------------------------------------------------------------+
| fuzzystrmatch | 1.1 | public | determine similarities and distance between strings |
+--------------------+---------+------------+--------------------------------------------------------------------+
| hll | 2.13 | public | type for storing hyperloglog data |
| hll | 2.14 | public | type for storing hyperloglog data |
+--------------------+---------+------------+--------------------------------------------------------------------+
| hstore | 1.6 | public | data type for storing sets of (key, value) pairs |
+--------------------+---------+------------+--------------------------------------------------------------------+
Expand Down
2 changes: 1 addition & 1 deletion cloud/availability.rst
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ distributed nodes.
For HA, any data that is written to a primary database called the Writer
is instantly replicated onto a secondary database called the Reader in
real-time, through a stream called a
`WAL <https://www.postgresql.org/docs/9.4/static/wal-intro.html>`__ or
`WAL <https://www.postgresql.org/docs/current/static/wal-intro.html>`__ or
Write-Ahead-Log.

To ensure HA is functioning properly, Citus Cloud runs health checks
Expand Down
4 changes: 2 additions & 2 deletions conf.py
Original file line number Diff line number Diff line change
Expand Up @@ -58,9 +58,9 @@
# built documents.
#
# The short X.Y version.
version = '9.4'
version = '9.5'
# The full version, including alpha/beta/rc tags.
release = '9.4'
release = '9.5'

# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
Expand Down
2 changes: 1 addition & 1 deletion develop/api_udf.rst
Original file line number Diff line number Diff line change
Expand Up @@ -1457,7 +1457,7 @@ Create a new shard to hold the lineitems for tenant 135:
citus_create_restore_point
$$$$$$$$$$$$$$$$$$$$$$$$$$

Temporarily blocks writes to the cluster, and creates a named restore point on all nodes. This function is similar to `pg_create_restore_point <https://www.postgresql.org/docs/10/static/functions-admin.html#FUNCTIONS-ADMIN-BACKUP>`_, but applies to all nodes and makes sure the restore point is consistent across them. This function is well suited to doing point-in-time recovery, and cluster forking.
Temporarily blocks writes to the cluster, and creates a named restore point on all nodes. This function is similar to `pg_create_restore_point <https://www.postgresql.org/docs/current/static/functions-admin.html#FUNCTIONS-ADMIN-BACKUP>`_, but applies to all nodes and makes sure the restore point is consistent across them. This function is well suited to doing point-in-time recovery, and cluster forking.

Arguments
*************************
Expand Down
8 changes: 4 additions & 4 deletions extra/enterprise-ms-sku.rst
Original file line number Diff line number Diff line change
Expand Up @@ -141,9 +141,9 @@ Debian/Ubuntu
.. code:: bash
sudo apt-get update
# Change to postgresql-11-citus-enterprise-9.4 if you want to install Citus for
# Change to postgresql-11-citus-enterprise-9.5 if you want to install Citus for
# PostgreSQL 11
sudo apt-get install -y postgresql-12-citus-enterprise-9.4
sudo apt-get install -y postgresql-12-citus-enterprise-9.5
Redhat/CentOS
~~~~~~~~~~~~~
Expand All @@ -153,8 +153,8 @@ remove the old package
.. code:: bash
# Change to citus-enterprise94_11 for PostgreSQL 11)
sudo yum install -y citus-enterprise94_12
# Change to citus-enterprise95_11 for PostgreSQL 11)
sudo yum install -y citus-enterprise95_12
.. _sku_setup:
Expand Down
8 changes: 4 additions & 4 deletions extra/enterprise.rst
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Ubuntu or Debian with Internet Access
sudo CITUS_REPO_TOKEN=XYZ bash
# install the server and initialize db
sudo apt-get install -y postgresql-12-citus-enterprise-9.4
sudo apt-get install -y postgresql-12-citus-enterprise-9.5
# preload citus extension
sudo pg_conftool 12 main set shared_preload_libraries citus
Expand All @@ -40,7 +40,7 @@ Ubuntu or Debian without Internet Access
sudo CITUS_REPO_TOKEN=XYZ bash
sudo apt-get clean
sudo apt-get install -y --download-only postgresql-12-citus-enterprise-9.4
sudo apt-get install -y --download-only postgresql-12-citus-enterprise-9.5
# go to package downloads
cd /var/cache/apt
Expand Down Expand Up @@ -82,7 +82,7 @@ Fedora, CentOS, or Red Hat with Internet Access
sudo CITUS_REPO_TOKEN=XYZ bash
# install PostgreSQL with Citus extension
sudo yum install -y citus-enterprise94_12
sudo yum install -y citus-enterprise95_12
# initialize system database (using RHEL 6 vs 7 method as necessary)
sudo service postgresql-12 initdb || \
Expand All @@ -107,7 +107,7 @@ Fedora, CentOS, or Red Hat without Internet Access
sudo CITUS_REPO_TOKEN=XYZ bash
# get package
sudo yum install --downloadonly --downloaddir=. citus-enterprise94_12
sudo yum install --downloadonly --downloaddir=. citus-enterprise95_12
# put them into a tarball
tar czf ~/citus-enterprise.tar.gz *.rpm
Expand Down
2 changes: 1 addition & 1 deletion index.rst
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
Citus Documentation
===================

Welcome to the documentation for Citus 9.4! Citus horizontally scales PostgreSQL across commodity servers using sharding and replication. Its query engine parallelizes incoming SQL queries across these servers to enable real-time responses on large datasets.
Welcome to the documentation for Citus 9.5! Citus horizontally scales PostgreSQL across commodity servers using sharding and replication. Its query engine parallelizes incoming SQL queries across these servers to enable real-time responses on large datasets.

.. raw:: html

Expand Down
2 changes: 1 addition & 1 deletion installation/multi_machine_debian.rst
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Steps to be executed on all nodes
::

# install the server and initialize db
sudo apt-get -y install postgresql-12-citus-9.4
sudo apt-get -y install postgresql-12-citus-9.5

# preload citus extension
sudo pg_conftool 12 main set shared_preload_libraries citus
Expand Down
2 changes: 1 addition & 1 deletion installation/multi_machine_rhel.rst
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Steps to be executed on all nodes
::

# install PostgreSQL with Citus extension
sudo yum install -y citus94_12
sudo yum install -y citus95_12
# initialize system database (using RHEL 6 vs 7 method as necessary)
sudo service postgresql-12 initdb || sudo /usr/pgsql-12/bin/postgresql-12-setup initdb
# preload citus extension
Expand Down
2 changes: 1 addition & 1 deletion installation/single_machine_debian.rst
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ This section describes the steps needed to set up a single-node Citus cluster on
curl https://install.citusdata.com/community/deb.sh | sudo bash

# install the server and initialize db
sudo apt-get -y install postgresql-12-citus-9.4
sudo apt-get -y install postgresql-12-citus-9.5


.. _post_install:
Expand Down
2 changes: 1 addition & 1 deletion installation/single_machine_rhel.rst
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ This section describes the steps needed to set up a single-node Citus cluster on
curl https://install.citusdata.com/community/rpm.sh | sudo bash

# install Citus extension
sudo yum install -y citus94_12
sudo yum install -y citus95_12

.. _post_install:

Expand Down
2 changes: 1 addition & 1 deletion use_cases/timeseries.rst
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ In a time-series workload, applications (such as some :ref:`distributing_by_enti

To deal with this workload, a single-node PostgreSQL database would typically use `table partitioning <https://www.postgresql.org/docs/current/static/ddl-partitioning.html>`_ to break a big table of time-ordered data into multiple inherited tables with each containing different time ranges.

Storing data in multiple physical tables speeds up data expiration. In a single big table, deleting rows incurs the cost of scanning to find which to delete, and then `vacuuming <https://www.postgresql.org/docs/10/static/routine-vacuuming.html>`_ the emptied space. On the other hand, dropping a partition is a fast operation independent of data size. It's the equivalent of simply removing files on disk that contain the data.
Storing data in multiple physical tables speeds up data expiration. In a single big table, deleting rows incurs the cost of scanning to find which to delete, and then `vacuuming <https://www.postgresql.org/docs/current/static/routine-vacuuming.html>`_ the emptied space. On the other hand, dropping a partition is a fast operation independent of data size. It's the equivalent of simply removing files on disk that contain the data.

.. image:: ../images/timeseries-delete-vs-drop.png
:alt: autovacuum removing part of a table, and a partition being erased
Expand Down

0 comments on commit 3d620cd

Please sign in to comment.