-
Notifications
You must be signed in to change notification settings - Fork 21
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
Update to Postgres 17 #54
base: master
Are you sure you want to change the base?
Conversation
@@ -1,5 +1,5 @@ | |||
comment = 'ulid type and methods' |
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.
Why are we renaming the extension?
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.
I'm only renaming the crate, because of the conflict, the build will generate a package that will provide 100% compatibility with the old name, so it won't break any existing Postgres extension
@@ -1,30 +1,32 @@ | |||
[package] | |||
name = "ulid" | |||
name = "pgx_ulid" |
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.
You shouldn't have a name conflict at all. Can you please describe the issue more?
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.
pgrx is trying to load the dynamic library ulid.so, but it is encountering the one from the ulid package and not from our extension, so I've renamed the crate to avoid any conflicts with the libraries generated
} | ||
} | ||
let inner = InnerUlid::from_string(val) | ||
.unwrap_or_else(|err| panic!("invalid input syntax for type ulid: \"{val}\": {err}")); |
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.
Don't we need to do ereport
?
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.
We don't
This is a big PR, to make it work with PG17 I had to rewrite many of the automatic functions from derive manually, but it works wonders with the latest version of Postgres. The biggest problem is the name conflict with the ulid package