Skip to content

Problem: unable to get the execution plan with select #807

Open

Description

@yrashk

This is problematic in tests and administrative functions, because we sometimes want just to extract something from the JSON output of the plan for testing purposes.

However, we don't have much choice but to use dblink and this would only work on objects already committed. Often not the case, especially in tests.

Proposed solution: implement explain function(s), returning json (and text?) of the plan

Should it go into omni_sql or some other extension? Do we need a new extension?

Activity

  1. yrashk commented on Mar 2, 2025

    @yrashk
    ContributorAuthor

    This can be easily done as a plpgsql function

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions