pgmq metadata #78
Merged
pgmq metadata #78
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ChuckHend
commented
Feb 4, 2023
Comment on lines
+134
to
+139
| let mut tx = self.connection.begin().await?; | ||
| let setup = query::init_queue(queue_name); | ||
| for q in setup { | ||
| sqlx::query(&q).execute(&mut tx).await?; | ||
| } | ||
| tx.commit().await?; |
There was a problem hiding this comment.
creating a queue now does a bunch of things, all are no-ops if the data already exists. metadata table, queue table, queue archive table, create index, insert metadata to queue metadata table
ChuckHend
requested review from
ryw,
ianstanton and
sjmiller609
as code owners
sjmiller609
approved these changes
Feb 4, 2023
Merged
sjmiller609
pushed a commit
that referenced
this pull request
Dec 5, 2023
* install ca-certificates with the Docker image * also remove package cache
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
enqueued_at- time the message hit the queueread_ctnumber of times the message has been read. if its >1 it usually means there's a problem somewhere in the applicationqueue.enqueue()toqueue.send(). This is easier to type and more in line with SQS and other messaging systems.pgmq_metadatatable. this contains one record for every queue and will be what we can query forlist_queues(). Currently only contains the name of the queues but will have other information later, like time created.pgmq_<queue_name>_archivetable. It won't be in use in this PR, but we will be addingqueue.archive()which will be the alternative toqueue.delete_message(). Instead of deleting the message completely, it will move it to the archive table.