Return to Question

1. is my approach fundamentally wrong?

2. PostgreSQL is claiming I'm having wal_level=minimal, how can I check the level of the produced WAL files? On the main server I get this when checking it's actual settings:

    select * from pg_settings where name='wal_level';
    -[ RECORD 1 ]------------------------------------------------
    name       | wal_level
    setting    | hot_standby
    unit       |
    category   | Write-Ahead Log / Settings
    short_desc | Set the level of information written to the WAL.
    extra_desc |
    context    | postmaster
    vartype    | enum
    source     | configuration file
    min_val    |
    max_val    |
    enumvals   | {minimal,archive,hot_standby}
    boot_val   | minimal
    reset_val  | hot_standby
    sourcefile | /.../postgresql.conf
    sourceline | 155
   

1. is my approach fundamentally wrong? Is there an alternative way to get this to work?

2. PostgreSQL is claiming I'm having wal_level=minimal, how can I check the level of the produced WAL files? On the main server I get this when checking it's actual settings:

    select * from pg_settings where name='wal_level';
    -[ RECORD 1 ]------------------------------------------------
    name       | wal_level
    setting    | hot_standby
    unit       |
    category   | Write-Ahead Log / Settings
    short_desc | Set the level of information written to the WAL.
    extra_desc |
    context    | postmaster
    vartype    | enum
    source     | configuration file
    min_val    |
    max_val    |
    enumvals   | {minimal,archive,hot_standby}
    boot_val   | minimal
    reset_val  | hot_standby
    sourcefile | /.../postgresql.conf
    sourceline | 155
   

wal_level = hot_standby

wal_level = hot_standby
archive_command = 'wal-e --s3-prefix=s3://... wal-push %p'

EDIT: adding details on archive_command on master