SHOW EXTENSIONS

The SHOW EXTENSIONS command lists the Extensions installed in the current or specified database.

Syntax

SHOW EXTENSIONS
[{FROM | IN} database]
[LIKE 'pattern']

Argument

  • FROM database or IN database: Lists the extensions in the specified database.

  • LIKE 'pattern': Returns a list of Extensions that match the specified pattern.

Remarks

  • Run the SHOW EXTENSIONS command without the FROM or IN clause to list all the Extensions in the current database.

  • Refer to the Permissions Matrix for the required permission.

Examples

  • List all the Extensions in the current database:

    SHOW EXTENSIONS;
    +----------------------+
    | Extensions_in_dbTest |
    +----------------------+
    | ts9                  |
    | str_to_ts9           |
    +----------------------+
  • List the Extensions in the specified database with names matching a specific pattern:

    SHOW EXTENSIONS FROM dbTest LIKE 't%';
    +---------------------------+
    | Extensions_in_dbTest (t%) |
    +---------------------------+
    | ts9                       |
    +---------------------------+

Last modified:

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.