From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | 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 Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [HACKERS] Custom compression methods |
Date: | 2020-10-22 11:40:27 |
Message-ID: | CAFiTN-v7ZFg2u0h+e+iBELafBBbAFOY9OKse1UxTS5HaSeB6Cw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Oct 21, 2020 at 8:51 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Thu, Oct 8, 2020 at 5:54 PM Tomas Vondra
> <tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
> > And is the oidvector actually needed? If we have the extra catalog,
> > can't we track this simply using the regular dependencies? So we'd have
> > the attcompression OID of the current compression method, and the
> > preserved values would be tracked in pg_depend.
>
> If we go that route, we have to be sure that no such dependencies can
> exist for any other reason. Otherwise, there would be confusion about
> whether the dependency was there because values of that type were
> being preserved in the table, or whether it was for the hypothetical
> other reason. Now, admittedly, I can't quite think how that would
> happen. For example, if the attribute default expression somehow
> embedded a reference to a compression AM, that wouldn't cause this
> problem, because the dependency would be on the attribute default
> rather than the attribute itself. So maybe it's fine.
Yeah, and moreover in the new patchset, we are storing the compression
methods in the new catalog 'pg_compression' instead of merging with
the pg_am. So I think only for the preserve purpose we will maintain
the attribute -> pg_compression dependency so it should be fine.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2020-10-22 11:48:21 | Re: Polyphase merge is obsolete |
Previous Message | Amit Kapila | 2020-10-22 11:35:05 | Re: Resetting spilled txn statistics in pg_stat_replication |