Re: [HACKERS] Point in Time Recovery - Mailing list pgsql-patches

From Tom Lane
Subject Re: [HACKERS] Point in Time Recovery
Date
Msg-id 16031.1090090426@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Point in Time Recovery  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: [HACKERS] Point in Time Recovery
List pgsql-patches
[ ... some desultory reading of PITR patch ... ]

What is the point of having both archive_program and archive_dest as
GUC variables?  Wouldn't it be simpler to fold them into one parameter,
viz

    archive_command = 'cp %s /archivedir'

For that matter, do we need a separate archive_mode boolean?  The one
thing I can positively guarantee about archive_dest (or archive_command)
is that we cannot come up with a useful default for it (no, /tmp isn't
good).  Therefore it does not seem very reasonable to let the user turn
on archiving without having explicitly specified an archive destination.

I propose that we fold all three GUC flags into a single archive_command
string whose built-in default is an empty string, and you enable
archiving by setting it to something nonempty.

            regards, tom lane

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: doc/src/sgml/ref/create_database.sgml had an extra tag
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Point in Time Recovery