-
Notifications
You must be signed in to change notification settings - Fork 18
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
PG16 Issues with Timescale Toolkit #47
Comments
Oh, and I think the formula needs to target toolkit v1.18.0 now instead of 1.17.0 too homebrew-tap/timescaledb-toolkit.rb Line 4 in 5f635cd
|
In case anybody needs to get timescale toolkit installed in the meantime, here's the absolutely insane way I went about it. First, open up the Homebrew formula (should be
Next, run Now we start manually running the commands that the formula would (essentially) do anyway, just with correct version numbers and such. curl -L https://github.com/pgcentralfoundation/pgrx/archive/refs/tags/v0.10.2.tar.gz -o cargo-pgrx.tar.gz
# then
mkdir pgrx
# then
tar -xzf cargo-pgrx.tar.gz -C pgrx
# then
cargo install --locked --path pgrx/pgrx-0.10.2/cargo-pgrx
# then
cargo pgrx init --pg16 pg_config
# then
cd extension
# then
cargo pgrx package
# then
cd .. Then we have to open up the post-install script from the toolkit code itself and edit it. However you prefer, but for VS code it's We'll edit line #119 from "so" to "dylib" and lines 192 and 193 both from ".so" to ".dylib". Then save and close the file. We'll now run that post-install script:
Now, since the brew shell wouldn't let me move the actual extension files into the PG directory (🙄), the next step is to get your current pwd
#=> /private/tmp/timescaledb-toolkit-20231207-79814-3k8arq Then open a new shell of your own (with your normal user access, not one spun up by Homebrew for you) separate from the brew shell. DO NOT close or exit the brew shell yet. If you do, Brew will automatically delete all files (clean up) the So, open up a new shell / console in a new tab / pane / etc. and let's manually copy the extension files from the # cp <from> <to>
cp /private/tmp/timescaledb-toolkit-20231207-79814-3k8arq/timescaledb-toolkit-1.18.0/target/release/timescaledb_toolkit-pg16/opt/homebrew/opt/postgresql@16/lib/postgresql/timescaledb_toolkit-1.18.0.dylib /opt/homebrew/Cellar/postgresql@16/16.1_1/lib/postgresql/
cp /private/tmp/timescaledb-toolkit-20231207-79814-3k8arq/timescaledb-toolkit-1.18.0/target/release/timescaledb_toolkit-pg16/opt/homebrew/opt/postgresql@16/share/postgresql@16/extension/timescaledb_toolkit--1.18.0.sql /opt/homebrew/Cellar/postgresql@16/16.1_1/share/postgresql@16/extension
cp /private/tmp/timescaledb-toolkit-20231207-79814-3k8arq/timescaledb-toolkit-1.18.0/target/release/timescaledb_toolkit-pg16/opt/homebrew/opt/postgresql@16/share/postgresql@16/extension/timescaledb_toolkit.control /opt/homebrew/Cellar/postgresql@16/16.1_1/share/postgresql@16/extension Then we can close the Homebrew console session (which will automatically clean up the |
Hey @jon-sully, thanks for documenting all your efforts here. It can be very useful for upgrading the actual instructions. Also, I can say I face the same as a Mac user and as an alternative I'm using the |
Howdy! I've had a hell of a couple of days trying to figure out what all is going on here, and I don't know that I'd even say I have successfully but I at least wanted to post back some notes.
So 3727aa7 bumped the Postgres version for TimescaleDB itself up to 16. 5f635cd quickly followed since the extension gets compiled as
.dylib
now, not a.so
, and I think those layers work fine — installing Timescale DB via Homebrew on a fresh Homebrew Postgres (16) works fine.Things do not work when you try to install the Toolkit after that. For starters, the Toolkit formula references PG15 instead of 16 in multiple places:
homebrew-tap/timescaledb-toolkit.rb
Line 10 in 5f635cd
homebrew-tap/timescaledb-toolkit.rb
Line 13 in 5f635cd
homebrew-tap/timescaledb-toolkit.rb
Line 27 in 5f635cd
homebrew-tap/timescaledb-toolkit.rb
Line 33 in 5f635cd
And hard-codes for the
.so
file extension here.Though perhaps more problematically, the post-install script for the toolkit itself (not this repo) still looks for
.so
here and hereAll of essentially prevent a new install of the Toolkit from running / working at all. 🙁
The text was updated successfully, but these errors were encountered: