| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: backup manifests |
| Date: | 2019-09-20 12:58:40 |
| Message-ID: | CA+TgmobNn98DdRcjRsm_Rqxt63584newD-U2Rs3Kt34aT=yJWQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 19, 2019 at 11:10 PM David Steele <david(at)pgmasters(dot)net> wrote:
> Overall we have found it's much simpler to label each backup and
> cross-check that against the pg version and system id. Start LSN is
> pretty unique, but backup labels work really well and are more widely
> understood.
I see your point, but part of my point is that uniqueness is not a
technical requirement. However, it may be a requirement for user
comprehension.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexey Kondratov | 2019-09-20 13:16:32 | Re: Conflict handling for COPY FROM |
| Previous Message | Jeff Janes | 2019-09-20 12:45:34 | WAL recycled despite logical replication slot |