| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, David Steele <david(at)pgmasters(dot)net>, Ildus Kurbangaliev <i(dot)kurbangaliev(at)gmail(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Custom compression methods |
| Date: | 2021-03-16 19:15:50 |
| Message-ID: | CA+TgmoZ+Shd6TtpsOLxyY6k5EKts9YToiV++mOuLJg9w_qr1bA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 16, 2021 at 11:21 AM Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
> If that is only the argument then it's possible today as well. I mean
> you can INSERT INTO .. SELECT FROM where source attribute as
> compressed data but the target attribute as external storage then also
> we will move the compressed data as it is to the target table.
Uggh. I don't like that behavior either, but I guess if it's the
long-established way things work then perhaps this is no worse.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2021-03-16 19:19:25 | Re: automatic analyze: readahead - add "IO read time" log message |
| Previous Message | Robert Haas | 2021-03-16 19:09:48 | Re: pg_amcheck contrib application |