| From: | Condor <condor(at)stz-bg(dot)com> |
|---|---|
| To: | Dorian Hoxha <dorian(dot)hoxha(at)gmail(dot)com> |
| Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org>, pgsql-general-owner(at)postgresql(dot)org |
| Subject: | Re: Uber migrated from Postgres to MySQL |
| Date: | 2016-07-27 07:15:07 |
| Message-ID: | e242aeacde03073495653e7c0ff4ff82@stz-bg.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 26-07-2016 21:04, Dorian Hoxha wrote:
> Many comments: https://news.ycombinator.com/item?id=12166585
> https://www.reddit.com/r/programming/comments/4uph84/why_uber_engineering_switched_from_postgres_to/
>
> On Tue, Jul 26, 2016 at 7:39 PM, Guyren Howe <guyren(at)gmail(dot)com> wrote:
>
>> Honestly, I've never heard of anyone doing that. But it sounds like
>> they had good reasons.
>>
>> https://eng.uber.com/mysql-migration/
>>
>> Thoughts?
>>
>> --
>> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general
They are right for upgrades.
It's a hard to shutdown 1 TB database and wait couple of days pg_upgrade
to finish upgrade and meanwhile database is offline.
In some distros after upgrade of PG version you don't have old binary
and library, need to do full dump and restore that take time and disk
space.
Regards,
Hristo S.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2016-07-27 07:17:58 | Re: Uber migrated from Postgres to MySQL |
| Previous Message | Michael Paquier | 2016-07-27 06:24:58 | Re: pg_dumping extensions having sequences with 9.6beta3 |