![]() 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |