On Fri, Oct 1, 2010 at 4:00 PM, Josh Berkus <j...@agliodbs.com> wrote: > > Our current arrangement of having a postgresql.conf file, a > recovery.conf file, and potentially a trigger file (during final > recovery) seems horribly hackish and impossible to manage neatly. >
all the contrary, IMHO what we have now seems *almost* fine... what we need to do is to have another standby side config file called maybe: standby.conf, otherwise we will end up with another huge configuration file ala postgresql.conf so we remove from recovery.conf what doesn't belong there... maybe is a good idea to put recovery_command on postgresql.conf (or in both files, recovery.conf and standby.conf, because they are no supposed to co-exist) if we have an standby server we use standby.conf, if we are recoverying a backup we use recovery.conf; and we can specify parameters in each situation (probably standby_mode should go away too because the only existence of a standby.conf file imply we are a standby but that is debatable) -- Jaime Casanova www.2ndQuadrant.com Soporte y capacitación de PostgreSQL -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
