EPrints Technical Mailing List Archive
Message: #05679
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] Database versions and Storage Engines
- To: <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] Database versions and Storage Engines
- From: Ian Stuart <Ian.Stuart@ed.ac.uk>
- Date: Mon, 9 May 2016 09:31:10 +0100
On 06/05/16 02:36, Matthew Brady wrote:
Hi All, Just wondering if there are any pros/cons for moving the tables from the default MyISAM to InnoDB. The DBA’s are wanting to upgrade MySQL to a newer version, and asked if swapping engines could also be performed. Is there any reasons I shouldn’t move away from the MyISAM engine??
I've run EPrints against PostgreSQL for close on 10 years. The only "problems" I've come across are1) that the *install* requires mysql (and you change to Pg after the install), and 2) I need to upgrade to Pg 9.3 to get live replication across multiple databases
-- Ian Stuart. Developer: ORI, RJ-Broker, and OpenDepot.org Bibliographics and Multimedia Service Delivery team, EDINA, The University of Edinburgh. http://edina.ac.uk/ This email was sent via the University of Edinburgh. The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
- References:
- [EP-tech] Database versions and Storage Engines
- From: Matthew Brady <Matthew.Brady@usq.edu.au>
- [EP-tech] Database versions and Storage Engines
- Prev by Date: [EP-tech] Software item type metadata.
- Next by Date: [EP-tech] Problems with the Coversheets plugin
- Previous by thread: [EP-tech] Database versions and Storage Engines
- Next by thread: Re: [EP-tech] Database versions and Storage Engines
- Index(es):