Raminder Singh

TLEs are like normal extensions in many ways and most of the information in [the docs](https://www.postgresql.org/docs/current/extend-extensions.html) applies to them as much as to normal extensions. A few differences worth noting...

If you published the upgrade files the users wouldn't be able make use of them due to the bug so It's best to wait. Yes, please leave the ticket open...

Looks like raw html is not supported currently. If I add set `skipHtml={true}` in the [props of the `ReactMarkdown` component](https://github.com/supabase/dbdev/blob/a764b6fa6fd013d9640c710ce292a2910d3cfcd7/website/components/ui/Markdown.tsx#L115-L126), the above README renders correctly. But this sounds dangerous because...

The latest code in this repo is not yet deployed on database.dev. It contains changes to the names of packages from `-` to `@`. E.g. `supabase-dbdev` on database.dev is named...

Currently we don't have a method to remove a TLE. We might add a command to `dbdev` CLI similar to `cargo yank` in future.

Hey @tiniscule, How did you install `basejump_core`? Did you use the `dbdev` cli's `install` command? If yes, was the `dbdev` version older than `0.1.4`? There was a fix in `0.1.4`...

> That second one seems odd, is that to be expected? Yes, that is ok. Postgres doesn't really understand the contents of a version. They are just treated a opaque...

Okay this is a `pg_tle` bug. You can reproduce it by running the following `pgtle` api calls: ```sql -- install version 1.0 of an extension SELECT pgtle.install_extension ( 'test123', '1.0',...

@ryan-managai since this is not yet fixed, reach out to support to get it fixed in your project.

If anyone's on the hosted version, could you please raise a support ticket. As @burmecia has pointed out, the pause/resume might have failed to restore permissions.