Bringing PostgreSQL towards zero downtime migration
Formal Metadata
| Title | Bringing PostgreSQL towards zero downtime migration |
|
| Alternative Title | Bringing PostgreSQL towards zero downtime migration with Python |
|
| Title of Series | |
| Part Number | 142 |
| Number of Parts | 173 |
| Author | |
| License | You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this license. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
| Production Place | Bilbao, Euskadi, Spain |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | Matthieu Rigal - Bringing PostgreSQL towards zero downtime migration with Python
Using an SQL database offers a bunch of advantages; first of all its
maturity and that it is understood by almost every software developer.
But it has at least one main disadvantage. As the data is structured,
if you want to modify the structure, for example on a long-running
project, you need a migration and therefore almost for sure, a
downtime.
When you have to make a migration, to modify the structure of data for
a small amount of records, it is so fast that it never gets
problematic. But if you think to modify the structure of tables
containing millions or billions of records, the time required to
simply apply the structural change is problematic.
Here are some changes we are working on at orderbird to go towards
zero downtime migrations using some of the latest improvements of
PostgreSQL 9.4, mainly logical replication and mixing in a little
magic of some python scripting with psycopg. |
|
| Keywords | |