-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We missed a place to update the cargo-pgx version. #442
Conversation
We really need to get a handle on this...
Why don't we run
but that means we miss breaking changes like the pgx upgrade. Any change to the inputs to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apparently when running sql-doctester under patch_build, the extension
needs to be DROPped first. Make tools/build DROP and switch to that.
From CI error message:
thread 'main' panicked at 'could not run init script: Error { ... message: "extension "timescaledb" does not exist" ... }', tools/sql-doctester/src/runner.rs:102:14
Do you want DROP EXTENSION IF EXISTS
?
Agreed. Thanks for leaving the comment hints in the appropriate places! Wonder what else we can do for this? |
That's probably a good idea so I added that, but the problem here was that BOTH extensions already exist. I reproduced that problem locally and now it's gone. Here goes... @JLockerman am I papering over a problem rather than fixing it? How was this supposed to work? Why didn't the extension exist last time you ran it, but now it does? |
Apparently when running sql-doctester under patch_build, the extension needs to be DROPped first. Make tools/build DROP and switch to that.
@epgts the doctester spins up a new DB for each file; I don't see how the extension could already be installed since we don't install it on the template. That said, I think the best way to avoid already-installed errors is probably to use |
Well both extensions are definitely already there :(
So I think I have only papered over a problem we need to instead
understand.
But no one needs this to work right now so I am going to file an issue and
leave it broken for now.
Thanks.
|
We really need to get a handle on this...