Re:Migrating 1200 databases from MySQL to Postgres
by cntlzw on Wednesday August 16, 2017 @10:10AM
(#15027565)
How concurrent is that? Can't imagine how writing to the file is even achieved.
[ Parent
| on HN ]
Re:Migrating 1200 databases from MySQL to Postgres
by zimpenfish on Wednesday August 16, 2017 @10:47AM
(#15027858)
"Badly". At least once a week someone managed to overwrite a change another client had just made. When I left, they were running a cron to copy it every minute as a "quick restore" when it happened.
Re:Migrating 1200 databases from MySQL to Postgres
by shoo on Wednesday August 16, 2017 @10:14AM
(#15027599)
maybe there is an email thread shared between all clients for acquiring / releasing the write lock on the xml file
Re:Migrating 1200 databases from MySQL to Postgres
by K-Wall on Wednesday August 16, 2017 @11:17AM
(#15028120)
Semaphore as a service Slack Chat bot.
Re:Migrating 1200 databases from MySQL to Postgres
by noir_lord on Wednesday August 16, 2017 @03:39PM
(#15030527)
Seen that.
Shared drive with excel files, people would shout at each other to 'release the lock'
Re:Migrating 1200 databases from MySQL to Postgres
by zimpenfish on Thursday August 17, 2017 @05:55AM
(#15035205)
Yeah, first real job had the customer database as a VB frontend onto an Access file shared over {whatever Win95 was using in 1996-97}. After a few snafus, the CS / Sales people learned that they had to single-task with the database.