Skip to content
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

adjust new_with_pool to return PGMQueue directly #217

Merged
merged 4 commits into from
May 21, 2024

Conversation

gruebel
Copy link
Contributor

@gruebel gruebel commented May 20, 2024

I'm not sure, if this was done on purpose, but new_with_pool(...) can't return an error, because the pool creation and initial connection is done beforehand. I changed it to just return itself 🙂

@ChuckHend
Copy link
Member

I'm not sure, if this was done on purpose, but new_with_pool(...) can't return an error, because the pool creation and initial connection is done beforehand. I changed it to just return itself 🙂

I think you're right, good idea!

Quick note: the Rust lib will publish to crates.io on merge to main, so CI will fail until we bump the version in Cargo.toml

@gruebel
Copy link
Contributor Author

gruebel commented May 21, 2024

@ChuckHend I don't think the failing test test_ext_create_list_drop has something to do with my changes. is it a known flaky test?

@ChuckHend
Copy link
Member

@ChuckHend I don't think the failing test test_ext_create_list_drop has something to do with my changes. is it a known flaky test?

Yea it is flaky. I re-ran it and now it has passed.

Do you want to bump the version in Cargo.toml so that we can release these changes when it merges to main?

@gruebel
Copy link
Contributor Author

gruebel commented May 21, 2024

Sure, can do. Should be version 0.27.0 or 0.26.2? The adjustment is not big, but it changes the signature of a public method.

@ChuckHend
Copy link
Member

Sure, can do. Should be version 0.27.0 or 0.26.2? The adjustment is not big, but it changes the signature of a public method.

Good call. Let's make it a minor release -> 0.27.0

@gruebel
Copy link
Contributor Author

gruebel commented May 21, 2024

@ChuckHend sorry for the delay, was not at my computer 😅 increased the version to 0.27.0

@ChuckHend
Copy link
Member

Thanks. I'm taking a look at that migration check now.

@ChuckHend
Copy link
Member

The order of columns returned by pgmq.list_queues() was changed in the v1.2.0 release. It's causing the sqlx cache check to fail. I'll push a fix for this quick.

old:

 queue_name | is_partitioned | is_unlogged |          created_at           
------------+----------------+-------------+-------------------------------
 x          | f              | f           | 2024-05-21 18:53:45.589962+00

new:

 queue_name |          created_at           | is_partitioned | is_unlogged 
------------+-------------------------------+----------------+-------------
 x          | 2024-05-21 18:56:11.791476+00 | f              | f

@ChuckHend
Copy link
Member

I went ahead and merged the fix for the sqlx cache back into this branch. All looks good.

Thank you @gruebel !

@ChuckHend ChuckHend merged commit 2702787 into tembo-io:main May 21, 2024
5 checks passed
@gruebel gruebel deleted the adjust-new-pool branch May 21, 2024 19:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants