| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Suraj Kharage <suraj(dot)kharage(at)enterprisedb(dot)com>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, Tels <nospam-pg-abuse(at)bloodgate(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>, vignesh C <vignesh21(at)gmail(dot)com> |
| Subject: | Re: documenting the backup manifest file format |
| Date: | 2020-05-15 15:05:02 |
| Message-ID: | 3ac28a9e-5ae5-ad0a-1b1e-0091c128dc6d@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/15/20 10:17 AM, Tom Lane wrote:
> David Steele <david(at)pgmasters(dot)net> writes:
>> On 5/15/20 9:34 AM, Tom Lane wrote:
>>> I vote for following the backup_label precedent; that's stood for quite
>>> some years now.
>
>> Of course, my actual preference is to use epoch time which is easy to
>> work with and eliminates the possibility of conversion errors. It is
>> also compact.
>
> Well, if we did that then it'd be sufficiently different from the backup
> label as to remove any risk of confusion. But "easy to work with" is in
> the eye of the beholder; do we really want a format that's basically
> unreadable to the naked eye?
Well, I lost this argument before so it seems I'm in the minority on
easy-to-use. We use epoch time in the pgBackRest manifests which has
been easy to deal with in both C and Perl, so experience tells me it
really is easy, at least for programs.
The manifest (to me, at least) is generally intended to be
machine-processed. For instance, it contains checksums which are not all
that useful unless they are checked programmatically -- they can't just
be eye-balled.
Regards,
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Muhammad Usama | 2020-05-15 15:54:03 | Re: Transactions involving multiple postgres foreign servers, take 2 |
| Previous Message | Masahiko Sawada | 2020-05-15 14:51:55 | Re: Transactions involving multiple postgres foreign servers, take 2 |