<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 11667 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 196, Issue 18<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Additional DB indices for Koha? (DevinimKoha)<br> 2. Re: Additional DB indices for Koha? (Fridolin SOMERS)<br> 3. Release maintenance: Monthly string freeze: shall it be<br> announced also on koha-devel and the general list?<br> (Victor Grousset/tuxayo)<br> 4. Re: Additional DB indices for Koha? (dcook@prosentient.com.au)<br> 5. The vendor does not exist at serials/subscription-add.pl<br> (Londhe Amar)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Wed, 23 Mar 2022 23:12:52 +0300<br>From: DevinimKoha <kohadevinim@devinim.com.tr><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Additional DB indices for Koha?<br>Message-ID: <89b6c5af-8ce3-ec03-363d-cab8db89660c@devinim.com.tr><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>Hi all,<br><br>Indexes and in generally speaking database performance tuning is quite <br>complex in some cases and is very related with your system, data, size <br>of customers, etc.<br><br>It is better to look at every system specifically.<br><br>In general, it is not true that indexes give performance everytime. I <br>may see, in many cases, indexes become a big issue in lots of databases <br>after a while.<br><br>As you mentioned, in some cases insert,updates can be quite slow in some <br>situations due to indexes.<br><br>On 22.03.2022 02:43, Victor/tuxayo wrote:<br>> Ah we use KEY to add indices!<br>> Thanks Fridolin and Tomas.<br>><br>> On 22-03-22 00:13, Tomas Cohen Arazi wrote:<br>>> We in fact might have too many indexes defined. This is a valid <br>>> hypothesis when the index size (on disk) is too close to the DB size <br>>> for a table.<br>><br>> That might also slow down inserts and updates or is that not significant?<br>><br>> Cheers,<br>><br><br><br>------------------------------<br><br>Message: 2<br>Date: Wed, 23 Mar 2022 10:16:54 -1000<br>From: Fridolin SOMERS <fridolin.somers@biblibre.com><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Additional DB indices for Koha?<br>Message-ID: <d1203054-2052-4496-9e04-619268088c53@biblibre.com><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>We add some issues with indexes on timestamp.<br>1 lines never have the exact same timestamp to the index is never <br>efficient right ?<br><br>Best regards,<br><br>Le 23/03/2022 à 10:12, DevinimKoha a écrit :<br>> Hi all,<br>> <br>> Indexes and in generally speaking database performance tuning is quite <br>> complex in some cases and is very related with your system, data, size <br>> of customers, etc.<br>> <br>> It is better to look at every system specifically.<br>> <br>> In general, it is not true that indexes give performance everytime. I <br>> may see, in many cases, indexes become a big issue in lots of databases <br>> after a while.<br>> <br>> As you mentioned, in some cases insert,updates can be quite slow in some <br>> situations due to indexes.<br>> <br>> On 22.03.2022 02:43, Victor/tuxayo wrote:<br>>> Ah we use KEY to add indices!<br>>> Thanks Fridolin and Tomas.<br>>><br>>> On 22-03-22 00:13, Tomas Cohen Arazi wrote:<br>>>> We in fact might have too many indexes defined. This is a valid <br>>>> hypothesis when the index size (on disk) is too close to the DB size <br>>>> for a table.<br>>><br>>> That might also slow down inserts and updates or is that not significant?<br>>><br>>> Cheers,<br>>><br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br><br>-- <br>Fridolin SOMERS <fridolin.somers@biblibre.com><br>Software and system maintainer 🦄<br>BibLibre, France<br><br><br>------------------------------<br><br>Message: 3<br>Date: Wed, 23 Mar 2022 23:47:22 +0100<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: koha-devel <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Release maintenance: Monthly string freeze:<br> shall it be announced also on koha-devel and the general list?<br>Message-ID: <a9078590-293a-ed7d-d1f7-fa2c96638cfb@tuxayo.net><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>Hi :)<br><br>The idea is to push the librarians, admins, and devs to check the <br>translations out if they remember something off. To try to reach out <br>instead of relying on those already interested in translation and <br>subscribed to koha-translate.<br><br>Currently not all release maintainers announce the string freeze in the <br>same place resulting in confusion.<br><br>Cheers,<br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Message: 4<br>Date: Thu, 24 Mar 2022 10:32:39 +1100<br>From: <dcook@prosentient.com.au><br>To: "'Fridolin SOMERS'" <fridolin.somers@biblibre.com>,<br> <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Additional DB indices for Koha?<br>Message-ID: <081d01d83f0e$54151730$fc3f4590$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Actually, having an index on a timestamp column can make searching much more efficient, because the indexed data is stored in sorted order by timestamp. That makes it quicker and easier to use a WHERE clause like "WHERE timestamp > date1". It can just do a binary search which is very efficient. Otherwise, the database needs to brute force the search by looping through every row, sorting the whole dataset by the timestamp, and then checking the condition. When you get into millions of rows and/or gigabytes of timestamped data, you really really want an index on that column. (Note: PostgreSQL is much better than MySQL for demonstrating this using the "EXPLAIN" and "ANALYZE" keywords, although it looks like MariaDB supports "ANALYZE" since 10.1.0 for evaluating queries using the same output format as "EXPLAIN"). <br><br>In general, if the table has a small amount of data, there's no advantage adding an index (unless it's something like a UNIQUE index). If the table is large or likely to grow, it can be useful to add an index to fields that will be used for searching:<br>- Tables like action_logs, old_issues, old_reserves, statistics, accountlines, linktracker log transactional data forever, so they're good to index as they'll grow over time and querying those tables will become more burdensome over time. Tables like items and biblio* probably make sense, because they could potentially be large. <br>- A small table like "letter", it probably doesn't need any additional indexes besides ones for foreign keys and unique indexes. (Funny that I randomly chose this table since Jonathan and Martin have recently updated the DB structure for this table along those lines.)<br><br>Of course, even with indexes, sometimes a query can request too much data, and it'll cause performance problems. The "Reports" module is dangerous like that actually. But that's a whole other thing...<br><br>Btw, if you want to see what indexes are defined for a MySQL table, you can just use "SHOW INDEXES from tablename". <br><br>In MySQL, you can also use non-standard "index hints": ( E.g. ANALYZE SELECT * FROM biblio FORCE INDEX (blbnoidx) WHERE biblionumber > 1; ). Generally this isn't necessary, but I have used it from time to time for specific MySQL SQL reports. <br><br>Anyway, that's my little rant on indexes 😅.<br><br>David Cook<br>Senior Software Engineer<br>Prosentient Systems<br>Suite 7.03<br>6a Glen St<br>Milsons Point NSW 2061<br>Australia<br><br>Office: 02 9212 0899<br>Online: 02 8005 0595<br><br>-----Original Message-----<br>From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Fridolin SOMERS<br>Sent: Thursday, 24 March 2022 7:17 AM<br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Additional DB indices for Koha?<br><br>We add some issues with indexes on timestamp.<br>1 lines never have the exact same timestamp to the index is never efficient right ?<br><br>Best regards,<br><br>Le 23/03/2022 à 10:12, DevinimKoha a écrit :<br>> Hi all,<br>> <br>> Indexes and in generally speaking database performance tuning is quite <br>> complex in some cases and is very related with your system, data, size <br>> of customers, etc.<br>> <br>> It is better to look at every system specifically.<br>> <br>> In general, it is not true that indexes give performance everytime. I <br>> may see, in many cases, indexes become a big issue in lots of <br>> databases after a while.<br>> <br>> As you mentioned, in some cases insert,updates can be quite slow in <br>> some situations due to indexes.<br>> <br>> On 22.03.2022 02:43, Victor/tuxayo wrote:<br>>> Ah we use KEY to add indices!<br>>> Thanks Fridolin and Tomas.<br>>><br>>> On 22-03-22 00:13, Tomas Cohen Arazi wrote:<br>>>> We in fact might have too many indexes defined. This is a valid <br>>>> hypothesis when the index size (on disk) is too close to the DB size <br>>>> for a table.<br>>><br>>> That might also slow down inserts and updates or is that not significant?<br>>><br>>> Cheers,<br>>><br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/ git : <br>> https://git.koha-community.org/ bugs : <br>> https://bugs.koha-community.org/<br><br>--<br>Fridolin SOMERS <fridolin.somers@biblibre.com> Software and system maintainer 🦄<br>BibLibre, France<br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/<br><br><br><br>------------------------------<br><br>Message: 5<br>Date: Thu, 24 Mar 2022 01:59:14 -0600<br>From: Londhe Amar <amar@ourlib.in><br>To: koha-devel@lists.koha-community.org<br>Subject: [Koha-devel] The vendor does not exist at<br> serials/subscription-add.pl<br>Message-ID: <3f2551e56ef45232e10d91cccf9d9724@ourlib.in><br>Content-Type: text/plain; charset="utf-8"; Format="flowed"<br><br><br><br>Home › Serials › New subscription<br>Unable to add new subscription in koha.<br><br>vendor is available in koha,<br>I am able to search for a vendor on the subscription edit form at <br>serials/subscription-add.pl, but when i select vendor and biblio and <br>click on next button it shows " The vendor does not exist " alert.<br><br>I have upgraded koha version 19.11 to 20.11.06.<br><br><br>Is there anything else I might want to examine that could be causing the <br>problem?<br><br><br>-- <br>Thanks and Regards,<br>Londhe Amar<br>Software developer<br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: Screenshot from 2022-03-24 13-25-56.png<br>Type: image/png<br>Size: 111479 bytes<br>Desc: not available<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220324/4853da5a/attachment.png><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 196, Issue 18<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>