Installing a new pg_tle extension version which requires following an upgrade path doesnt' work
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- postgresql
- Domain
- databases
Research direction
Start by reproducing the clean-install case with create extension "basejump_core" version '2.1.0' and the reported basejump_core--2.0.1.sql and basejump_core--2.0.1--2.1.0.sql files. Read the pg_tle documentation and compare its upgrade-path behavior with the PR linked in the report; done means version 2.1.0 installs without a dedicated basejump_core--2.1.0.sql file.
Written by the indexing model from the issue text.
Description
Bug report
I have 2 files for my extension.
basejump_core--2.0.1.sql
basejump_core--2.0.1--2.1.0.sql
Default version set to 2.1.0.
On a clean install, running create extension "basejump_core"
version '2.1.0'; will fail with the following error:
ERROR: could not find sql function "basejump_core--2.1.0.sql" for extension basejump_core in schema pgtle
Based on the pg_tle docs, this appears like it should work by first installing 2.0.1 and then following the 2.1.0 path - but doesn't seem to.
To Reproduce
Here's a PR with the upgrade I'm working on which doesn't work: https://github.com/usebasejump/basejump/pull/57
Expected behavior
I expect the extension to be installable to 2.1.0 without having a dedicated basejump_core--2.1.0.sql extension file
- Dominant language
- TypeScript
- Stars
- 443
- Forks
- 31
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/dbdev
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·