![]() Erlang/OTP and Elixirįrom now, Erlang/OTP 25 is supported. ![]() ![]() There are also new equivalent commands to delete old MAM messages. Two companion commands are added: delete_old_messages_status to check the status of the batch operation, and abort_delete_old_messages to abort the batch process. Now you can use delete_old_messages_batch, which performs the operation in batches, by setting the number of messages to delete per batch and the desired rate of messages to delete per minute. If you use the command delete_old_messages periodically and noticed it can bring your system to an undesirable state with high CPU and memory consumption… The oauth_revoke_token API command has changed its returned result. To fix an existing PostgreSQL database schema, apply those changes manually: ALTER TABLE archive DROP CONSTRAINT i_archive_sh_peer ĪLTER TABLE archive DROP CONSTRAINT i_archive_sh_bare_peer ĬREATE INDEX i_archive_sh_username_peer ON archive USING btree (server_host, username, peer) ĬREATE INDEX i_archive_sh_username_bare_peer ON archive USING btree (server_host, username, bare_peer) ĪLTER TABLE push_session DROP CONSTRAINT i_push_session_susn ĬREATE UNIQUE INDEX i_push_session_susn ON push_session USING btree (server_host, username, service, node) ĪLTER TABLE mix_pam DROP CONSTRAINT i_mix_pam ĪLTER TABLE mix_pam DROP CONSTRAINT i_mix_pam_us ĬREATE UNIQUE INDEX i_mix_pam ON mix_pam (username, server_host, channel, service) ĬREATE INDEX i_mix_pam_us ON mix_pam (username, server_host) ĪLTER TABLE route DROP CONSTRAINT i_route ĬREATE UNIQUE INDEX i_route ON route USING btree (domain, server_host, node, pid) ĪLTER TABLE mqtt_pub DROP CONSTRAINT i_mqtt_topic ĬREATE UNIQUE INDEX i_mqtt_topic_server ON mqtt_pub (topic, server_host) If you moved your PostgreSQL database from old to new schema using mod_admin_update_sql or the update_sql API command, be aware that those methods forgot to perform some updates. WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ĬREATE INDEX ON (jid) To update an existing database, depending on the schema used to create it:ĬREATE INDEX i_muc_room_host_created_at ON muc_room(host(75), created_at) ĬREATE INDEX i_muc_room_subscribers_jid USING BTREE ON muc_room_subscribers(jid) ĬREATE INDEX i_muc_room_host_created_at ON muc_room USING btree (host, created_at) ĬREATE INDEX i_muc_room_subscribers_jid ON muc_room_subscribers USING btree (jid) ĬREATE INDEX i_muc_room_host_created_at ON muc_room (host, created_at) ĬREATE INDEX i_muc_room_subscribers_jid ON muc_room_subscribers(jid) ĬREATE INDEX ON (host, nick) Those indexes can be added in the database before upgrading to 22.05, that will not affect older versions. Two new indexes were added to optimize MUC. There are no breaking changes in configuration, and only one change in commands API.Ī more detailed explanation of those topics and other features: New Indexes in SQL for MUC When upgrading from the previous version please notice: there are minor changes in SQL schemas, the included rebar and rebar3 binaries require Erlang/OTP 22 or higher, and make rel uses different paths. – Improved MQTT, MUC, and ConverseJS integration A new ejabberd release is finally here! ejabberd 22.05 includes five months of work, 200 commits, including many improvements (MQTT, MUC, PubSub, …) and bug fixes.
0 Comments
Leave a Reply. |