Cascading replication and archive_command

From: Michael Renner <michael(dot)renner(at)amd(dot)co(dot)at>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Cascading replication and archive_command
Date: 2014-05-05 13:19:41
Message-ID: BA03FD4E-0326-4717-A76C-D4FF984CDEBB@amd.co.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

apparently a few users were puzzled that archive_command is ignored on slave servers, which comes as a surprise since streaming replication will work fine from slaves and as far as I’ve checked the documentation also doesn’t point out the fact that archive_command gets a different treatment.

Is this intentional or an oversight? Should this be fixed in the code (feature parity to SR) or in the documentation making this more explicit?

best,
Michael

[1] http://serverfault.com/questions/514136/postgresql-archive-command-on-a-cascading-standby-server as well as personal contacts

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2014-05-05 13:27:23 Re: folder:lk/lk date:yesterday..
Previous Message Heikki Linnakangas 2014-05-05 13:08:42 Re: Fix initdb for path with whitespace and at char