Re: Crash in BRIN minmax-multi indexes

From: Zhihong Yu <zyu(at)yugabyte(dot)com>
To: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
Subject: Re: Crash in BRIN minmax-multi indexes
Date: 2021-03-31 18:20:20
Message-ID: CALNJ-vSxOD2aUMZ7vTLSXUh_bgkzyLAbHST4cXxFpd7a8O6dsQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,
In build_distances():

a1 = eranges[i].maxval;
a2 = eranges[i + 1].minval;

It seems there was overlap between the successive ranges, leading to
delta = -6785000000

FYI

On Wed, Mar 31, 2021 at 10:30 AM Jaime Casanova <
jcasanov(at)systemguards(dot)com(dot)ec> wrote:

> Hi,
>
> Just found $SUBJECT involving time with time zone and a subselect. I
> still don't have narrowed to the exact table/index minimal schema but
> if you run this query on the regression database it will creash.
>
> ```
> update public.brintest_multi set
> timetzcol = (select tz from generate_series('2021-01-01'::timestamp
> with time zone, '2021-01-31', '5 days') tz limit 1)
> ;
> ```
>
> attached a backtrace. Let me know if you need extra information.
>
> --
> Jaime Casanova
> Director de Servicios Profesionales
> SYSTEMGUARDS - Consultores de PostgreSQL
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2021-03-31 18:27:39 Re: Crash in BRIN minmax-multi indexes
Previous Message Tom Lane 2021-03-31 18:12:52 Re: ModifyTable overheads in generic plans