Skip to content

UNNEST can't handle multiple arrays #3507

Open

Description

@danthegoodman1

Version

1.26.0

What happened?

See linked playground. If you make it a single array it works fine.

Supported since postgres 9.4

Relevant log output

function unnest(unknown, unknown, unknown) does not exist

Database schema

No response

SQL queries

No response

Configuration

No response

Playground URL

https://play.sqlc.dev/p/177bd0ee17908bc7f1a1e1fe4302562aa99013a7f3a6e3d0b6d92a50bb7d8fd3

What operating system are you using?

No response

What database engines are you using?

PostgreSQL

What type of code are you generating?

Go

Activity

  1. added
    bugSomething isn't working
    triageNew issues that hasn't been reviewed
    on Jul 26, 2024
  2. removed
    triageNew issues that hasn't been reviewed
    on Aug 5, 2024
  3. added a commit that references this issue on Dec 6, 2024
    722c78d
  4. icedream commented on Jun 10, 2025

    @icedream

    I've seen the PR has been around since December. Would it get the PR accepted quicker if someone else were to test with their own SQL? I've noticed this being an issue, and the change looks very simple and logical.

  5. judofyr commented on Jul 7, 2025

    @judofyr

    Are there any known workarounds here?

  6. jordanst3wart commented on Mar 25, 2026

    @jordanst3wart

    Relates to: #958
    bad workaround with JSONB mentioned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions