Time |
Nick |
Message |
07:12 |
|
rjackson_isl joined #evergreen |
09:24 |
|
stephengwills joined #evergreen |
10:57 |
|
jvwoolf joined #evergreen |
11:00 |
stephengwills |
Is it reasonable for me to upgrade EG database on a test server and copy the database to a production server and expect the prod version to attach to it and work properly? (as opposed to upgrading the prod database in place?) |
11:02 |
stephengwills |
i’m having profound index problems this morning and want to start by checking the basic premise of my workflow. |
11:08 |
|
khuckins joined #evergreen |
11:49 |
|
terran joined #evergreen |
11:54 |
bshum |
stephengwills: That makes sense to me. "Production" is basically whichever database you designate as the main one used by your Evergreen app servers. |
11:54 |
bshum |
It doesn't have to be the same actual database server, etc. |
11:55 |
bshum |
of course, once people start using said database, it'd be hard to go back and use another DB copy again |
11:55 |
bshum |
Meaning copying transactions, etc. between databases, I wouldn't advise that |
11:55 |
bshum |
But basically any app server, you can edit the opensrf.xml config to point at any database you want |
11:56 |
bshum |
In theory. :) |
11:57 |
bshum |
In the past, I've "upgraded" databases by building a whole fresh server and new PG version, and then took a db-dump copy of our prod database and restored it into the fresh system. |
11:57 |
bshum |
I just liked doing the dump/restore PG approach rather than doing in-place pg_upgrade. But to each their own. |
11:59 |
bshum |
Of course, your "test server" becoming the new production, you'll want to make sure the hardware is comparable, tuning is done, security in place, etc. |
11:59 |
bshum |
Good luck with everything. Be curious to hear how it all turns out later. :) |
13:08 |
|
hbrennan joined #evergreen |
14:18 |
stephengwills |
in 3.1.8 I imported a record via z39.50, added a 250 field and clicked save. There was no UX feedback that I was successful until I click on MARC View and saw that my 250 field has, indeed been added. is this a known problem? |
16:51 |
|
khuckins_ joined #evergreen |
17:18 |
|
jvwoolf left #evergreen |
22:01 |
|
finnx joined #evergreen |
22:01 |
|
finnx left #evergreen |
22:55 |
|
finnx joined #evergreen |
23:23 |
|
sandbergja joined #evergreen |