Bug 29938 - Allow a secondary database
Summary: Allow a secondary database
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Database (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-25 11:31 UTC by paxed
Modified: 2022-02-11 07:17 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description paxed 2022-01-25 11:31:01 UTC
Our database has two servers, primary and secondary where the data is replicated from primary to secondary. Koha can only use the primary, which means the secondary is sitting idle.

Allow defining a secondary database server in koha-conf.

Allow executing some queries in the secondary instead of the primary one. Specifically, the saved reports would have the most benefit here:

1) Reports only do selects, never anything that changes the database, so are safe to do on the secondary server.
2) Normally, running very heavy reports can affect Koha use. If the queries were executed on the secondary server, they would have no effect on Koha.
3) It generally doesn't matter if report data is few minutes old.