Database migrations

Major version upgrade

In order to perform a major database upgrade, you will need to stop database replication so you can perform the necessary upgrade and restart your database.

Steps to do major version upgrades w/o data loss:

If you are using Postgres, make sure to drop the replication slot after you paused the Artie deployment. See the Postgres tips section for more information.

Schedule an application downtime and pause your application.
Check that Artie is no longer processing any data from our Analytics portal and pause your Artie deployment.
Perform the database upgrade and restart your database server.
Resume your Artie deployment.
Resume your application and rotate Artie offsets.

Minor version upgrade

Minor version upgrades do not require stopping database replication. This should be automatically handled by your database provider and applied during your maintenance window.

Questions

For Postgres, you can run this query to see all the replication slots on the server:

SELECT
    slot_name,
    wal_status,
    pg_size_pretty(
        pg_wal_lsn_diff(
        pg_current_wal_lsn(), restart_lsn)) AS retained_wal,
    active,
    restart_lsn FROM pg_replication_slots;

Ensure that active is false and then drop the replication slot.

SELECT pg_drop_replication_slot('artie');

Database

​Major version upgrade

​Minor version upgrade

​Questions

Major version upgrade

Minor version upgrade

Questions