Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) is available now. It will be promoted to general availability (GA) soon and at that time it will be renamed to SingleStore 10.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10, while SingleStore 9.0 is recommended for production workloads.

LMV_JOIN_OPTIMIZATION_RESULTS

This view contains information about the results of join optimization operations. This table displays rows for each query plan and each table joined in the query plan.

Column Name

Description

ACTIVITY_NAME

The activity name of the query plan. This corresponds to ACTIVITY_NAME in mv_activities.

QUERY_TEXT

The text of the query.

DATABASE_NAME

The name of the related database.

TABLE_NAME

The name of a table within a given join.

IS_LOCAL

Whether or not a given join is local.

SEQ_NUMBER

The sequence number of this row among the rows for this query plan.

TABLE_COUNT

The number of tables included in a given join.

TABLE_INDEX

The position of the table in its join.

FILTER_SELECTIVITY

The estimated fraction of rows that satisfy the filter conditions on a given table (not including conditions involving multiple tables, i.e. join conditions)

JOIN_SELECTIVITY

The estimated fraction of rows that satisfy the join conditions.

TABLE_CARD

The estimated rowcount of the table.

CARD_POST_FILTER

The estimated rowcount of the table after filter conditions on this table only.

CARD_POST_JOIN

The estimated rowcount of the join so far after joining this table.

COST_SO_FAR

The estimated cost of executing a given join so far, according to the optimizer’s cost model.

Last modified:

Was this article helpful?

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In