| From: | Ildus Kurbangaliev <i(dot)kurbangaliev(at)postgrespro(dot)ru> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Ildar Musin <i(dot)musin(at)postgrespro(dot)ru> |
| Subject: | Re: [HACKERS] Custom compression methods |
| Date: | 2017-12-01 21:55:52 |
| Message-ID: | 20171202005552.0aa06476@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 1 Dec 2017 16:38:42 -0300
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-12-01 21:59:25 | Re: [HACKERS] proposal: psql command \graw |
| Previous Message | Alvaro Herrera | 2017-12-01 21:53:40 | Re: [HACKERS] Custom compression methods |