| From: | Daniel Farina <daniel(at)heroku(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: backup_label during crash recovery: do we know how to solve it? |
| Date: | 2012-01-01 22:01:34 |
| Message-ID: | CACN56+MOG_OS2DQqYEw3HPDui2nZoHD9x=bhq=Fe1e7reQoH5A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jan 1, 2012 at 5:18 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> That's awfully complicated. If we're going to require co-operation from the
> backup/archiving software, we might as well just change the procedure so
> that backup_label is not stored in the data directory, but returned by
> pg_start/stop_backup(), and the caller is responsible for placing it in the
> backed up copy of the data directory (or provide a new version of them to
> retain backwards compatibility). That would be a lot simpler.
That's also entirely acceptable. In fact, I like it.
+1
--
fdr
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Farina | 2012-01-01 22:09:52 | Re: backup_label during crash recovery: do we know how to solve it? |
| Previous Message | Andrew Dunstan | 2012-01-01 21:05:34 | Re: alternate psql file locations |