From: Ildus Kurbangaliev <i.kurbangaliev@postgrespro.ru>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org, Ildar Musin <i.musin@postgrespro.ru>
Subject: Re: [HACKERS] Custom compression methods
Date: Sat, 2 Dec 2017 00:55:52 +0300
Message-ID: <20171202005552.0aa06476@postgrespro.ru> (raw)
In-Reply-To: <20171201193842.c47t6tyi72rhgdll@alvherre.pgsql>
References: <6ac2d002-94a7-feab-301d-e790417b43a9@2ndquadrant.com>
<20171201193842.c47t6tyi72rhgdll@alvherre.pgsql>
On Fri, 1 Dec 2017 16:38:42 -0300
Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>
> To me it makes sense to say "let's create this method which is for
> data compression" (CREATE ACCESS METHOD hyperz TYPE COMPRESSION)
> followed by either "let's use this new compression method for the
> type tsvector" (ALTER TYPE tsvector SET COMPRESSION hyperz) or "let's
> use this new compression method for the column tc" (ALTER TABLE ALTER
> COLUMN tc SET COMPRESSION hyperz).
>
Hi, I think if CREATE ACCESS METHOD can be used for compression, then it
could be nicer than CREATE COMPRESSION METHOD. I just don't
know that compression could go as access method or not. Anyway
it's easy to change syntax and I don't mind to do it, if it will be
neccessary for the patch to be commited.
--
----
Regards,
Ildus Kurbangaliev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: i.kurbangaliev@postgrespro.ru, alvherre@alvh.no-ip.org, tomas.vondra@2ndquadrant.com, i.musin@postgrespro.ru
Subject: Re: [HACKERS] Custom compression methods
In-Reply-To: <20171202005552.0aa06476@postgrespro.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox