Re: Small issues with CREATE TABLE COMPRESSION

From: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jacob Champion <pchampion(at)vmware(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Small issues with CREATE TABLE COMPRESSION
Date: 2021-05-05 05:13:11
Message-ID: CAFiTN-uPc8OojZh6eRuO9WCOqN7Gi3_V=MhQAe=LZKm03yT=2w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 29, 2021 at 9:31 AM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
>
> On Tue, Apr 27, 2021 at 03:22:25PM +0900, Michael Paquier wrote:
> > Hi all,
>
> > And so, ALTER MATERIALIZED VIEW supports SET COMPRESSION but this is
> > not mentioned in its docs:
> > https://www.postgresql.org/docs/devel/sql-altermaterializedview.html
> >
> > psql could have tab completion support for that.
>
> Actually ALTER matview ALTER col has no tab completion at all, right ?

Right.

> Good point. I started with this.
>
> diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
> index 39927be41e..8cceea41d0 100644
> --- a/doc/src/sgml/ref/alter_table.sgml
> +++ b/doc/src/sgml/ref/alter_table.sgml
> @@ -391,7 +391,21 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
> </term>
> <listitem>
> <para>
> - This sets the compression method for a column. The supported compression
> + This sets the compression method to be used for data inserted into a column.
> +
> + This does not cause the table to be rewritten, so existing data may still
> + be compressed with other compression methods. If the table is rewritten with
> + <command>VACUUM FULL</command> or <command>CLUSTER</command>, or restored
> + with <application>pg_restore</application>, then all tuples are rewritten
> + with the configured compression methods.
> +
> + Also, note that when data is inserted from another relation (for example,
> + by <command>INSERT ... SELECT</command>), tuples from the source data are
> + not necessarily detoasted, and any previously compressed data is retained
> + with its existing compression method, rather than recompressing with the
> + compression methods of the target columns.
> +
> + The supported compression
> methods are <literal>pglz</literal> and <literal>lz4</literal>.
> <literal>lz4</literal> is available only if <literal>--with-lz4</literal>
> was used when building <productname>PostgreSQL</productname>.

Your documentation looks fine to me.

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2021-05-05 05:20:09 Re: AlterSubscription_refresh "wrconn" wrong variable?
Previous Message Craig Ringer 2021-05-05 04:20:04 Re: [PATCH] Identify LWLocks in tracepoints