You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, if we just create schema in postgres; it should work, isn't it?
I've heard of some users using the SQL directly to install the objects in this extension. However, the migration scripts are generally not executable directly and are intended to be run with the alter extension pgmq update command. I have not done this myself.
@ChuckHend When it's all sql based; no dependency etc then it would be great for wide compatibility to make it sql only. It would be great if schema is maintained as a single sql file for these cases.
@ChuckHend When it's all sql based; no dependency etc then it would be great for wide compatibility to make it sql only. It would be great if schema is maintained as a single sql file for these cases.
Thanks
If you want to help out, /~https://github.com/tembo-io/pgmq/blob/main/pgmq-extension/sql/pgmq.sql contains all the functions and DDL (except the create schema statement, I think). For anyone looking to run this as SQL-only, that is the best place to start. Help is very much welcome here!
Please click this link and upvote & follow to help Microsoft to add/approve pgmq as a supported Postgres extension:
Add extension pgmq - https://feedback.azure.com/d365community/idea/9d5c7e3b-f35f-ef11-a4e6-6045bdbe5235?q=pgmq
Raw text link: https://feedback.azure.com/d365community/idea/9d5c7e3b-f35f-ef11-a4e6-6045bdbe5235?q=pgmq
The text was updated successfully, but these errors were encountered: