Closed ChuckHend closed 3 weeks ago
## 💎 $150 bounty • Tembo
### Steps to solve:
1. Start working: Comment
/attempt #302
with your implementation plan2. Submit work: Create a pull request including
/claim #302
in the PR body to claim the bounty3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts
Thank you for contributing to tembo-io/pgmq!
Add a bounty • Share on socials
Attempt | Started (GMT+0) | Solution |
---|---|---|
🟢 @Saturn225 | Oct 17, 2024, 1:19:53 PM | WIP |
🟢 @Neptune650 | Oct 17, 2024, 3:51:30 PM | #319 |
/attempt #302
Algora profile | Completed bounties | Tech | Active attempts | Options |
---|---|---|---|---|
@Saturn225 | 1 bounty from 1 project | Rust, Scala, HTML |
Cancel attempt |
Can I get this assigned? @ChuckHend
/attempt #302
Algora profile | Completed bounties | Tech | Active attempts | Options |
---|---|---|---|---|
@Neptune650 | 2 bounties from 2 projects | C++, C, Python & more |
Cancel attempt |
💡 @Neptune650 submitted a pull request that claims the bounty. You can visit your bounty board to reward.
implemented in https://github.com/tembo-io/pgmq/pull/319
🎉🎈 @Neptune650 has been awarded $150! 🎈🎊
https://github.com/tembo-io/pgmq/blob/2783a6b6d61f0f9a65a0b6cfa109d88066ce7992/pgmq-extension/sql/pgmq.sql#L453 takes in a parameter designating whether the queue to drop is partitioned. When that flag is true, pgmq will handle deleting the objects/records from pg_partman as well. So if you run
pgmq.drop_queue()
on a partitioned queue without the flag, there will be some orphaned pg_partman stuff laying around.the
pgmq.meta
table has an attribute that tracks whether table is partitioned. So on the drop_queue() call, I think we should drop thepartitioned
and replace it with a query to something likeselect is_partitioned from pgmq.meta where ....