Re: [HACKERS] Custom compression methods - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: [HACKERS] Custom compression methods
Date
Msg-id CAFiTN-s_h5+ZYhRBru8i+OJU3HPgMk1mY0BmwwER12SGCq=SxA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Custom compression methods  (Jaime Casanova <jcasanov@systemguards.com.ec>)
Responses Re: [HACKERS] Custom compression methods
List pgsql-hackers
On Wed, Mar 24, 2021 at 1:22 PM Jaime Casanova
<jcasanov@systemguards.com.ec> wrote:
>
> On Fri, Mar 19, 2021 at 2:44 PM Robert Haas <robertmhaas@gmail.com> wrote:
> >
> > I committed the core patch (0003) with a bit more editing.  Let's see
> > what the buildfarm thinks.
> >
>
> I think this is bbe0a81db69bd10bd166907c3701492a29aca294, right?
> This introduced a new assert failure, steps to reproduce:
>
> """
> create table t1 (col1 text, col2 text);
> create unique index on t1 ((col1 || col2));
> insert into t1 values((select array_agg(md5(g::text))::text from
> generate_series(1, 256) g), version());
> """
>
> Attached is a backtrace from current HEAD

Thanks for reporting this issue.  Actually, I missed setting the
attcompression for the expression index and that is causing this
assert.  I will send a patch in some time.

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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
Next
From: Justin Pryzby
Date:
Subject: Re: PoC/WIP: Extended statistics on expressions