INTERNAL Error: Attempted to access index 3 within vector of size 3 | LAST_VALUE ignore nulls

[littlegreenbean33]

What happens?

INTERNAL Error:
Attempted to access index 3 within vector of size 3

Stack Trace:

/home/julian/.duckdb/cli/latest/duckdb() [0x910443]
...
/home/julian/.duckdb/cli/latest/duckdb() [0x716413]
/lib/x86_64-linux-gnu/libc.so.6(+0x2a1ca) [0x76588a62a1ca]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x8b) [0x76588a62a28b]
/home/julian/.duckdb/cli/latest/duckdb() [0x719cd7]

-----------------------------------------
 Error in watcher: {"exception_type":"FATAL","exception_message":"Failed: database has been invalidated because of a previous fatal error. The database must be restarted prior to being used
 again.\nOriginal error: \"Failed: database has been invalidated because of a previous fatal error. The database must be restarted prior to being used again.\nOriginal error: \"Failed: datab
ase has been invalidated because of a previous fatal error. The database must be restarted prior to being used again.\nOriginal error: \"Failed: database has been invalidated because of a pr
evious fatal error. The database must be restarted prior to being used again.\nOriginal error: \"Attempted to access index 3 within vector of size 3\"\"\"\""}
                                                               Will now terminate.
                                                                                  libva info: VA-API version 1.20.0 
                    libva info: Trying to open /snap/firefox/5987/gnome-platform/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
                               libva info: Found init function __vaDriverInit_1_20
                                                                                  libva info: va_openDriver() returns 0 
D

To Reproduce

/home/julian/.duckdb/cli/latest/duckdb

v1.2.1 8e52ec4395 
Enter ".help" for usage hints.

DROP TABLE IF EXISTS FOOTER;
CREATE TABLE FOOTER 
  ( 
      id             INT PRIMARY KEY, 
      car            VARCHAR(20),
      length         INT, 
      width          INT,
      height         INT
  );

INSERT INTO FOOTER VALUES (1, 'Hyundai Tucson', 15, 6, NULL); 
INSERT INTO FOOTER VALUES (2, NULL, NULL, NULL, 20);
INSERT INTO FOOTER VALUES (3, NULL, 12, 8, 15);
INSERT INTO FOOTER VALUES (4, 'Toyota Rav4', NULL, 15, NULL); 
INSERT INTO FOOTER VALUES (5, 'Kia Sportage', NULL, NULL, 18);
SELECT
      LAST_VALUE(car) over ( )  last_car,
      LAST_VALUE(car order by id ignore nulls) over ( )  last_car,
  FROM FOOTER; 

INTERNAL Error:
Attempted to access index 3 within vector of size 3

OS:

ubuntu 24.04 intel x64

DuckDB Version:

1.2.1

DuckDB Client:

CLI

Hardware:

No response

Full Name:

julian colomina

Affiliation:

none

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have not tested with any build

Did you include all relevant data sets for reproducing the issue?

Yes

Did you include all code required to reproduce the issue?

• Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

• Yes, I have
• [ ]

[szarnyasg]

Hi @littlegreenbean33, thanks for reporting this! I can reproduce it with DuckDB 1.2.1 but cannot reproduce it with the nightly release of DuckDB:

Stable release

v1.2.1 8e52ec4395
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
D  related to #15307
D DROP TABLE IF EXISTS FOOTER;
D CREATE TABLE FOOTER
    (
        id             INT PRIMARY KEY,
        car            VARCHAR(20),
        length         INT,
        width          INT,
        height         INT
    );
D
D INSERT INTO FOOTER VALUES (1, 'Hyundai Tucson', 15, 6, NULL);
D INSERT INTO FOOTER VALUES (2, NULL, NULL, NULL, 20);
D INSERT INTO FOOTER VALUES (3, NULL, 12, 8, 15);
D INSERT INTO FOOTER VALUES (4, 'Toyota Rav4', NULL, 15, NULL);
D INSERT INTO FOOTER VALUES (5, 'Kia Sportage', NULL, NULL, 18);
D SELECT
        LAST_VALUE(car) over ( )  last_car,
        LAST_VALUE(car order by id ignore nulls) over ( )  last_car,
    FROM FOOTER;
INTERNAL Error:
Attempted to access index 3 within vector of size 3

Preview release

v1.3.0-dev2110 7912713493
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
D DROP TABLE IF EXISTS FOOTER;
D CREATE TABLE FOOTER
    (
        id             INT PRIMARY KEY,
        car            VARCHAR(20),
        length         INT,
        width          INT,
        height         INT
    );
D
D INSERT INTO FOOTER VALUES (1, 'Hyundai Tucson', 15, 6, NULL);
D INSERT INTO FOOTER VALUES (2, NULL, NULL, NULL, 20);
D INSERT INTO FOOTER VALUES (3, NULL, 12, 8, 15);
D INSERT INTO FOOTER VALUES (4, 'Toyota Rav4', NULL, 15, NULL);
D INSERT INTO FOOTER VALUES (5, 'Kia Sportage', NULL, NULL, 18);
D SELECT
        LAST_VALUE(car) over ( )  last_car,
        LAST_VALUE(car order by id ignore nulls) over ( )  last_car,
    FROM FOOTER;
┌──────────────┬──────────────┐
│   last_car   │   last_car   │
│   varchar    │   varchar    │
├──────────────┼──────────────┤
│ Kia Sportage │ Kia Sportage │
│ Kia Sportage │ Kia Sportage │
│ Kia Sportage │ Kia Sportage │
│ Kia Sportage │ Kia Sportage │
│ Kia Sportage │ Kia Sportage │
└──────────────┴──────────────┘

I don't think this is related to #15307, which occurs with recursive common table expressions.

[szarnyasg]

Feel free to reopen if this reproduces on the main branch.

[littlegreenbean33]

I was just wondering if you found the root cause ? or this was closed because it does not appear in nightly ? do we know why did happened, when/how was fixed, what tests were added to monitor this does not happen again ? This is a bug in production/stable.

edit:

I just reproduced the error using first_value query. For me this renders first_value/last value windows functions essentially non-working. Firmly believe the problem runs deeper. I may be unsophisticated SQL user but I have many decades in the trade. I would not close the issue with a clear root cause analysis.

EDIT: both issues do not occur on 1.2.2 any more.