Lovable Cloud refuses CREATE EXTENSION

What it means in plain English

Lovable's changelog for October 13, 2026, under "Supported PostgreSQL extensions on Lovable Cloud," says Lovable Cloud databases support a fixed set of PostgreSQL extensions, such as pg_cron, pg_net, vector, and postgis. Lovable refuses CREATE EXTENSION for any other extension, in the project chat, the SQL editor, and the Lovable API, and builds the feature with plain SQL instead. Extensions already installed in the database keep working.

The changelog gives those four names as examples of the fixed set. It does not say they are the whole set.

Likely causes

• The project chat, the SQL editor, or the Lovable API was asked to CREATE EXTENSION for an extension outside the fixed set. Those are the three places the changelog names.
• The feature can be built with plain SQL. That is what the changelog says Lovable does instead.
• An extension that is already installed is outside this change. The changelog says those keep working.

How to fix it, step by step

1. Read where the refusal happened. The changelog names the project chat, the SQL editor, and the Lovable API.
2. If the extension is already installed, leave it. The changelog says installed extensions keep working.
3. For an extension Lovable refuses, use the plain-SQL version of the feature. The changelog says that is what Lovable builds instead of running CREATE EXTENSION.
4. The examples Lovable lists for the supported set are pg_cron, pg_net, vector, and postgis. The entry says "such as," so those names are examples, not a complete list printed in the changelog.
5. This refusal is not a preview or publish failure. Those are separate pages: Lovable: Live preview couldn't start and Lovable app is a blank white or black screen after publish.

How to check it worked

• Lovable is no longer being asked to CREATE EXTENSION for an extension outside the fixed set.
• The feature runs as plain SQL, or it uses an extension the changelog says is already installed.

Sources

• https://docs.lovable.dev/changelog (opens in a new tab)