We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It is related to reported issue #177 (#177).
Proposed solution hasn't resolved the problem once It has already been installed prx 0.12.5 and we faced same reported error (#177) message:
pgvectorscale]# cargo pgrx --version cargo-pgrx 0.12.5
Do you know if there is any additional reason about this below error? Error: cargo pgrx install --release 0: Not a directory (os error 20)
0.80
15
OEL 8.8
Source
On prem/Self-hosted
Please refer issue #177 for further details: https://github.com/timescale/pgvectorscale/issues/177.
🆘 No, could someone else please work on the bugfix?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happened?
It is related to reported issue #177 (#177).
Proposed solution hasn't resolved the problem once It has already been installed prx 0.12.5 and we faced same reported error (#177) message:
pgvectorscale]# cargo pgrx --version
cargo-pgrx 0.12.5
Do you know if there is any additional reason about this below error?
Error:
cargo pgrx install --release
0: Not a directory (os error 20)
pgvectorscale extension affected
0.80
PostgreSQL version used
15
What operating system did you use?
OEL 8.8
What installation method did you use?
Source
What platform did you run on?
On prem/Self-hosted
Relevant log output and stack trace
Please refer issue #177 for further details: https://github.com/timescale/pgvectorscale/issues/177.
How can we reproduce the bug?
Please refer issue #177 for further details: https://github.com/timescale/pgvectorscale/issues/177.
Are you going to work on the bugfix?
🆘 No, could someone else please work on the bugfix?
The text was updated successfully, but these errors were encountered: